mastodon-e2ee-specification VS documentation

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

The Fediverse is inherently difficult to understand and use. Their documentation, sadly, is written as a sales pitch for the federation piece of it, but doesn’t make it simple to understand. This summary is better, but parts of the explanation still don’t make sense when trying to access content. I couldn’t figure out how to see Mastodon toots from other servers, as an example.

My next task is triaging and labelling issues and pull requests in the documentation repo on GitHub, with an aim to bring in as many of those existing contributions as we can. I am particularly focused on the API, and I am not currently so familiar with other topics (Mastodon server installation, administration, etc), so I'll be relying on additional help! I am aware that some of the issues and PRs have been waiting for a while, but I'll do what I can to get things improved here.

that said, you can achieve what you're asking but it's tricky: https://github.com/mastodon/documentation/blob/archive/Running-Mastodon/Serving_a_different_domain.md

I recommend you go through their documentation. It's very well written. https://docs.joinmastodon.org/

I honestly begin going to the Mastodon docs and reading. https://docs.joinmastodon.org/

https://github.com/mastodon/documentation documentations are here. I guess you can upload your documentation in the manner in the style as seen there. Although the documentation that you want is more related to code.

Anyhow, if you want to really learn what it is about, their docs are actually good at explaining that https://docs.joinmastodon.org/, but it is definitely too much for normal people.

Before I dive in too far, let's talk about microblogging and federation as Mastodon describes it. For microblogging, the Mastodon docs say:

The only other issue I hit was getting certbot to work. I found the answer to that little problem via an update in this GitHub issue (namely: disable the site altogether, run certbot in standalone mode, and then enable the site and update the certs section). I need to push a PR for this as well, but wording it will be a pain.