this post was submitted on 06 Aug 2025
138 points (99.3% liked)
Technology
75295 readers
4317 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
First, if I were to take a guess I would assume that it can be coded to give the AI read/write access to messages because it’s part of the encryption protocol without giving it to Meta as a company? I really have no idea because I don’t write code or deal with backend stuff so it’s just an idea.
Second, I’m not defending the tech company. I’m coming up with a hypothesis as to why something may be possible. I’m not saying it’s probable.l because we both know that Meta will find any way to gain access to data by doing any sort of shady shit they can.
The concept of "End to End Encryption" (E2EE) is that one end encrypts the data, it passes through transport, and the only person who can read the decrypted data is the intended receiver.
In the case of WhatsApp, this should mean:
The whole "Meta AI summaries" thing has to run on their servers. Large language models small enough to fit on a phone don't produce sensible output yet, and your phones battery would drain very quickly. Since each message is (supposed to be) encrypted with different keys, no human nor computer can make sense of the encrypted data without the keys to decrypt it. For their servers to provide a "summary of your chats", they have to be able to read the content of the messages. Thus proving that the whole "end to end encryption" in WhatsApp is either false, or made entirely useless with them sending all messages to themselves without E2EE.
The only proof that would invalidate this is evidence of the LLM running locally on device. Even then, the way some of WhatsApp's services work (like notifications, WhatsApp Web) creates some serious doubt on the "E2EE" claim.
It is absolutely essential that any communications platform claiming "E2EE" proves this by making the client-side code (the stuff running on your device) fully open source. A proprietary app, like WhatsApp, by definition makes it harder to fully understand its inner workings, and thus fully verify the E2EE claim.
You should have read your link before typing all this. Their E2EE is a bit similar to OMEMO and Signal in the sense that one device is really like one contact, and one chat between two people is really like a group chat with many members associated with two identities. So they are adding another optional endpoint where you send the message to get that summary.
Of course if you do send it, it's readable by them no matter what they say.
Of course proprietary encryption (I'd argue that even proprietary code) can't be trusted to do what declared.
But there is no logical contradiction whatsoever between their claim of having E2EE and this functionality.
Wow! Thanks for this response. That makes a lot of sense as to how it’s done.