mastodon-e2ee-specification VS joinmastodon

No end to end encryption in mastodon: 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).

This is a very hard problem to solve. I know it's being worked on by some smart people though, see https://soatok.blog/2022/11/22/towards-end-to-end-encryption-for-direct-messages-in-the-fediverse/

Related: https://soatok.blog/2022/11/22/towards-end-to-end-encryption...

The good news is that because Mastodon is open source, and development is done in the open, anyone with the needed skills and interest could implement it right, and there is a project spearheaded by cryptography experts to do just that. https://github.com/soatok/mastodon-e2ee-specification

Now you have some more work to do, and probably some more money in the project, will you be delegating the development of the joinmastodon.org to a team to take advantage of UX input?

There used to be some svgs and a press-kit with images in the joinmastodon repository, but they've removed them for some reason and only have pngs now: https://github.com/mastodon/joinmastodon/tree/master/public/illustrations You can find some svg source files poking around in the history.