this post was submitted on 13 Mar 2026
589 points (99.3% liked)
Technology
82591 readers
4205 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
They could always do that, and basically anything you can read on your phone, they can access if they need.
Encryption is a math thing: generate a pair of keys: one te encde, one to decode. I broadcast the one to encode ("public key"), and the whole world is tu use it to send me encrypted messages. I keep the decoding ("private key") only for myself.
In client to erver encryption, we exchange keys with the server through which go all the comms: it decodes my messages and re-encodes them for my contact.
In e2e, the key exchange is between contacts: the server does not have the private keys.
In Meta, the proprietary app can send your private key to the server and then they know what you wrote. You have no way to know it doesn't do so!
Opensource audited software is the only way to make sure.