3 ms·
If you give your messages to a service provider of course they can read it. Same as if you give your messages to twitter, facebook, your telecom operator or any
by SahAssar 4y ago
If you give your messages to a service provider of course they can read it. Same as if you give your messages to twitter, facebook, your telecom operator or anyone else. Either make sure that the party is trustworthy or make sure the service is end-to-end encrypted.
- throwaway0x7E6 4y agoyeah, but it was trivial to implement E2EE, and I'd expect such a recent protocol to have it
- Kye 4y agoThere's work on it, and implementing it at the protocol level may not be as easy, obvious, or as helpful as it seems. https://github.com/soatok/mastodon-e2ee-specification https://github.com/soatok/mastodon-e2ee-specification https://twitter.com/LeaKissner/status/1592937764684980224 https://twitter.com/LeaKissner/status/1592937764684980224
- SahAssar 4y agoWhy do you think it's trivial to implement E2EE? It's extremely complicated to do it in a way that works well, and handling things like backup/restore of messages, how to handle key recovery in case of lost devices/logins, how to allow parties to verify each other are all extremely complicated questions both technologically and socially.
- throwaway0x7E6 4y agothe alternative to those inconveniences is random peole running your instance being able to read your correspondence
- SahAssar 4y agoSo you don't have an answer to why you think it's trivial to implement E2EE?
- throwaway0x7E6 4y agoit would've been during development, yeah. less so now, with many servers already deployed. it would be a clusterfuck like the email.