Submitted 8 hours ago by deadsuperhero@lemmy.world to fediverse@lemmy.world
https://wedistribute.org/2026/02/fediverse-e2ee-coming/
Important progress has been made regarding bringing MLS end-to-end encryption to the ActivityPub protocol, with developers already building implementations and providing feedback to a future version of the protocol spec.
I thought we already had Matrix
We do.
This is for activitypub DMs.
That’s what I mean.
The headline is a lie.
And XMPP before it, even if for e2ee messaging. At least this is a slightly different use case.
Matrix is decentralized but its not federating in a way like activity pub is doing
ActivityPub isn’t the only way to federate.
It’s federating the same way email does. Anyone can spin up their own server. And if they want anyone can spin up their own software.
How so? It’s certainly very similar.
The matrix protocol enables federation between different instances running different homeservers between users using different clients.
What do you mean?
And what benefit justifies yet another standard?
Matrix is a poor choice from a cryptographic perspective. With some serious issues historically (some of which are still unfixed to this day), and an extremely poor response to disclosures.
I have a bit of an issue with the title, considering federated end to end encrypted messaging has existed since, at the latest, 1991.
What’s the messaging protocol?
Pgp is protocol agnostic, you can use it over email, xmpp, irc… Over pretty much anything that supports plugins.
It’s usually used for email tho.
Well now this sounds interesting. And I assume it’s open source?
🤯 That gave me pause. Would non-FOSS even be an option for anything ActivityPub?
It seems so, as the project (Emissary) is using the GNU Affero GPL.
@benpate@mastodon.technology that’s amazingly quick work after just under four weeks. I’m looking forward to the result.
We should always have more alternatives to chose from - good to see so many players.
MLS will eventually be included in all messengers.
It was initially introduced by Wire as an RFC, but they fumbled the federation by making it an enterprise only feature. Because of that, other messengers will do the federating for them. iMessage, Google Messenger, Matrix, and Germ DM (Bluesky) do or partly have it implemented.
Finally I can discuss my scat fetish with my fellow scat enthusiasts away from the prying eyes of the NSA!
Nyeh-heh heh heeh!
Let’s gooooooo
Why?
What benefit does this have over Signal/Matrix?
The article just says “improvements”.
why? because it would be cool if only intended recipients are able to view sent messages.
That’s not really going to be the case if you’re using a website instead of an audited app like signal/matrix.
So, I used messaging here in the broad sense. One possible application for it is instant messaging, which there are ActivityPub implementations out there doing that. But it can also be used for statuses or pretty much anything else that gets federated.
That actually sounds cool, I wonder if they could support Hidden containers, so the same message can be decypted to different messages by different users.
One benefit is that Signal controls all the infrastructure and some people do not like that. Sure, you could also spin up a Matrix home server, but that isn’t an ideal solution for everyone either. Some people want to do messaging via their existing ActivityPub infrastructure and that’s OK.
from what i can tell, mls supports much larger group chats (50k users) whereas i assume signal would struggle.
my chat of 10 people i signal seems just as secure, if i am reading right.
But, what about Session? It’s decentralized, E2EE, uses Lokinet, seems pretty solid, no?
No phone, email, or other info needed to sign up
Major League Soccer messaging? Let’s goooo
good news everybody!
odama626@lemmy.world 33 minutes ago
Also XMPP with omemo?