Notices by Raphael Robert (raphaelrobert@mastodon.social)

LinkedIn annonced that it will use your data to train AI models, and craftily chose to use an opt-out mechanism. Deactivate this in your settings now, if you don’t want to give away your content.

Not long ago, someone (who is likely the founder of SimpleX Chat) wrote a blog post about MLS that contained a pretty blatant factual mistake about MLS' authentication, including an alleged lack of security. Thankfully, @soatok took the time to debunk that: https://soatok.blog/2025/08/25/barking-up-the-ratchet-tree-mls-is-neither-royal-nor-nude/

The MLS Architecture document – the companion document to the MLS Protocol document – is now finally available as RFC 9750:

https://www.rfc-editor.org/info/rfc9750

🔐 Discord introduces end-to-end encryption with Messaging Layer Security (MLS) 🔐

Im really happy to see another large scale MLS deployment. It shows the technology is fit for purpose.

Discord uses MLS for key negotiation in group calls with really fine-grained Forward Secrecy and Post-Compromise Security: A new member of the group cannot decrypt any media sent in the previous epochs, and a leaving member of the group cannot decrypt any media sent in future epochs.

https://discord.com/blog/meet-dave-e2ee-for-audio-video

@silverpill @phoenix_r_d @krille No, and I don’t remember that it ever was seriously proposed.
The MIMI documents are here: https://datatracker.ietf.org/group/mimi/documents/

@krille @silverpill @phoenix_r_d Not sure what you mean. Substantial parts of the MIMI protocol have been proposed by US, the matrix folks and the Wire folks. The IETF process is very transparent. Anyone can participate, either by just observing or actively contributing. All decisions and discussions are written down. That makes it easy to debunk false claims like yours :)

@krille @phoenix_r_d That’s why we helped start the IETF MIMI working group to get everyone around the table

@krille @phoenix_r_d Yes, neither the matrix protocol nor XMPP protect metadata well enough unfortunately.

@krille @phoenix_r_d We've been having extensive discussions about this in various IETF groups, with both Matrix and XMPP folks. We are very open to either adhering to existing standards or helping shape new ones. Sometimes you have to start fresh though, that's exactly what we did with MLS and MIMI. I don't see why this couldn't be repeated for s c2s protocol. Either way, join the working groups and propose your ideas!

@crepererum @delta @stillgreenmoss @ben @besendorf I can say that MLS works well in a federated environment. Federation has always been part of the picture during the design phase. The fact it doesn’t work in Matrix yet is a Matrix problem, not an MLS problem. MLS is part of the (newish) federated MIMI spec and it also works in our stack. Of course it’s still early days for MLS, but it’s already deployed by e.g. Cisco Webex.

MLS finally has a logo…

… and stickers!

Let's make this crystal clear: If you think you are anonymous because you

- used a throwaway number for Signal
- picked a completely random username for Wire/Matrix
- were given a random username with Threema/Session

YOU ARE NOT! You can be identified by the push tokens that are registered with each messenger operator.

https://chaos.social/@andre_meister/111538429318672330

MLS is now finished! 5 years of intense exchange with industry and academia, what a great group effort. Congratulations and thanks to all those who contributed!

We wrote an overview about it here:
https://blog.phnx.im/rfc-9420-mls/