mastodon-e2ee-specification

> If someone sends me their profile link that's not on my instance, I can't actually reply to it. Instead, I need to go to my Mastodon instance and then search for that link in order to actually have an interactable version of that "tweet". Actually, you have options: https://mstdn.social/@feditips/109507990803168318 > And I have no idea if I chose the right Mastodon instance with the right hall admins that won't read my private messages and ban me for having the wrong opinion. I'm working on that. https://github.com/soatok/mastodon-e2ee-specification

What Moxie wrote was about his decisions with Signal. It's not that relevant to this post for distinct two reasons: 1. One of the stated anti-tenets of what I'm proposing is competing with Signal. https://github.com/soatok/mastodon-e2ee-specification#anti-t... 2. Cryptography has matured greatly since Moxie wrote that post. I feel confident about rolling out a v1 E2EE protocol for the Fediverse in 2023, and then a v2 in 2024 or later. Migration is a two-putt, but it's tractable. I've worked on similar message format migrations before. 1. Roll out read-only support for v2. 2. Enable writing. Now people can start using v2. 3. Later, once the new version is ubiquitous for the scope of your concern, disable v1. It's not as fast as if you own the whole stack (like Signal does), but a federated ecosystem can move. Email is a lost cause. Activi

There'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://twitter.com/LeaKissner/status/1592937764684980224