←back to thread

Let's talk about AI and end-to-end encryption

(blog.cryptographyengineering.com)
174 points chmaynard | 2 comments | 17 Jan 25 05:50 UTC | HN request time: 0s | source
Show context
jFriedensreich ◴[17 Jan 25 17:03 UTC] No.42740367[source]▶
I think this has also a silver lining. The E2E encryption movement especially for messenger apps was largely also used to silently lock users out of their own data and effectively prevent user agency to use their own data to move apps, write automations or archive, this is not just true for whatsapp (the data export feature does not fully work since its launch and was just made to appease some EU law that did not properly check if the button works until the end.) Also signal does not have a way to do this. Maybe with ai coming into the game companies finally decide to provide access to data, I just hope it's in a transparent way with user opt in and user control.
replies(2): >>42740689 #>>42741345 #
1. do_not_redeem ◴[17 Jan 25 17:21 UTC] No.42740689[source]▶
1. Is data encrypted in transit?

2. Can the user access their data at rest?

Those two things are entirely orthogonal.

I don't think you can extrapolate a trend from a few apps having bugs in their export code. Google Takeout is also notoriously buggy and they don't use E2E encryption. A more likely explanation is companies of all kinds don't care that much about export functionality, due to the incentives involved.

replies(1): >>42741746 #
2. jFriedensreich ◴[17 Jan 25 18:37 UTC] No.42741746[source]▶
you CAN extrapolate from nearly all e2e encrypted apps not giving a way to use the data. And there is a big difference between buggy google export features or facebook actively making export unusable to lock in users.