mastodon-e2ee-specification VS mastodon

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

I'm the admin of a small server, which I set up a few months ago with the one-click install and then migrated to glitch-soc (https://glitch-soc.github.io/docs/). Recently I tried updating it to the new version of glitch-soc due to recent security updates. However I seem to have broken my server.

I imagine it might turn out to be something similar to https://glitch-soc.github.io/docs/

Have a look at glitch - a fork of Mastodon that looks and feels and behaves mostly just like mastodon but has Markdown support.

A good start to see Mastodons upstream finally implement features considered so necessary that they existed in a fork for years beforehand[0].

I'm not trying to sound cynical, this is legit a good change. Other fedi implementations have supported different message formatting (mainly markdown) for ages and that shit still degrading away to plaintext on Mastodon is extremely aggravating if you decide to (for example) use a bulletpoint list.

[0]: https://glitch-soc.github.io/docs/

You don't have to maintain a soft fork; Glitch-soc is a "friendly fork" which shares maintainers with upstream and has lots of great features, including a configurable post length limit.

What the fuck is your problem? Why do you some here just to see? Are you so fucking retarded that you don't think this issue have been brought up before? Do you think I'm just making up this on the spot? https://github.com/glitch-soc/mastodon/pull/1502 https://github.com/GlitchCatFedi/Policy/blob/main/Global%20Fulltext%20Search.markdown

Can we expect to see any of the https://glitch-soc.github.io/docs/ features coming to Mastodon mainline soon? Post formatting? Highlighting of misleading links? or local only posting?

Mastodon Glitch Edition

So this one is a fork, and infosec.exchange is a fork (https://github.com/glitch-soc/mastodon); are the mastodon committers opposed to incorporating those changes, or this fork situation is "as it should be" while these experiments run their course?

I'm all for experimentation, but since "the exodus" I've become acutely aware of how many instances are out there advertising their version number, so the first big rails (or mastodon itself) vuln is going to be some ooooonooooz