Emissary along with @Bonfire and @swf are working on #MLS based e2ee messaging over #ActivityPub supported by Sovereign Tech Fund
@benpate is now showing off Atlas Maps
Emissary along with @Bonfire and @swf are working on #MLS based e2ee messaging over #ActivityPub supported by Sovereign Tech Fund
I've just sent the first end-to-end-encrypted #MLS messages from one #Emissary instance to another.
News from around the USA really has me down, so it's important to celebrate the little wins 🎉
And, there's still so much to do. But with equal quantities of luck and caffeine, I can screencast some early prototypes for you before too long.
I believe #E2EE is important for the #Fediverse because it will give us more ways to use this network, and expand what people can do here.
I've just sent the first end-to-end-encrypted #MLS messages from one #Emissary instance to another.
News from around the USA really has me down, so it's important to celebrate the little wins 🎉
And, there's still so much to do. But with equal quantities of luck and caffeine, I can screencast some early prototypes for you before too long.
I believe #E2EE is important for the #Fediverse because it will give us more ways to use this network, and expand what people can do here.
I've just sent the first end-to-end-encrypted #MLS messages from one #Emissary instance to another.
News from around the USA really has me down, so it's important to celebrate the little wins 🎉
And, there's still so much to do. But with equal quantities of luck and caffeine, I can screencast some early prototypes for you before too long.
I believe #E2EE is important for the #Fediverse because it will give us more ways to use this network, and expand what people can do here.
I consider this a failure on our part but I don’t really know what to do about it. Most arguments against #XMPP don’t hold if you’re building from scratch anyway:
• #Conversations_im looks very outdated: OK, but you are developing your own clients anyway.
• XMPP doesn’t have an SDK: Neither does your #ActivityPub or email stack
• OMEMO is insecure and I would prefer #MLS: Yes, let’s work on that together and you’ll still benefit from XMPP’s 100+ solved IM problems.
@tris there are three actively developed protocols for federated instant messaging (XMPP, Matrix, Deltachat). At least one of them is very open to new developers and new ideas and has a structure in place to collaboratively work on those ideas and bring various stake holders together. With no disrespect to that individual I don't see why there needs to be a forth protocol loosely based on ActivityPub.
@tris Soatak is an expert in cryptography. I’m not. I’m more than happy to stand on the shoulder of giants when it comes to E2EE. That’s why we used the Signal Protocol 10+ years ago for #OMEMO and are now looking towards #MLS. However, good, interoperable protocol design is so much more than just E2EE. And maybe I've learned a thing or two about protocol design in my career that they don’t necessarily know.
As a community, we often ask ourselves how to attract more users to #XMPP. Yet the real tragedy is that people would rather build something entirely new (loosely based on email or #ActivityPub) than consider XMPP. Need end-to-end encryption by default? If compatibility with existing XMPP clients is a secondary concern, you can implement it in your own solution while still benefiting from our two decades of experience in instant messaging.
I consider this a failure on our part but I don’t really know what to do about it. Most arguments against #XMPP don’t hold if you’re building from scratch anyway:
• #Conversations_im looks very outdated: OK, but you are developing your own clients anyway.
• XMPP doesn’t have an SDK: Neither does your #ActivityPub or email stack
• OMEMO is insecure and I would prefer #MLS: Yes, let’s work on that together and you’ll still benefit from XMPP’s 100+ solved IM problems.
Do you see sport content on the Social Web?
Sport is one of the biggest industries in the world. Not only does it provide entertainment, it builds communities.
But, we're wondering, how much sport content do you see here and what kind? Is it sports content that is relevant to you? What other sport content would you like to see?
Please feel free to share your thoughts in the replies and boost for more to get involved! ⚾
#SocialWeb #Sport #Poll #Fediverse #Mastodon #Sports #Football #F1 #Hockey #Rugby #Athletics #Chess #Running #Tennis
@newsmast I have enjoyed seeing sports content here for the recent #MLS Cup finals and #MLB World Series! It was nice to see people live-tooting through it. Both were major cultural events, especially here in Canada because in both cases there was a Canadian team in the matchup.
I have also been pleasantly surprised to find some #PWHL fans here! Women's hockey fans are everywhere 😁 🏒🏒🏒
One big way I get sports content on here is via the @cbcnews feed. I get a lot of my regular Canadian news from there, too. @Flipboard has been doing a great job at bringing news sources to the fediverse.
I’m sad that we lost, but we had a good run. Let’s fucking run it back next year, and WIN THIS SHIT. LETS GO LOONS!!!! #mnufc #MLS #MastodonFC #loons #MLSCupPlayoffs
Major League Soccer will change its competition schedule in 2027 to align with the world's top leagues in a decision commissioner Don Garber called one of the most important in the history of the 30-year-old league. https://www.japantimes.co.jp/sports/2025/11/14/soccer/mls-to-change-schedule/?utm_medium=Social&utm_source=mastodon #soccer #mls #dongarber
My old #Rust in #Android team just published a blog post showing Android continues to improve #security by pushing for more memory safe code: https://security.googleblog.com/2025/11/rust-in-android-move-fast-fix-things.html
The results are amazing: Android now writes more Rust than C++, and the **Rust changes land faster** due to fewer revisions and faster code reviews. Medium and large changes are **rolled back about 4 times less** than changes written in C++.
I think this is also the first time that the use of #MLS in #RCS is mentioned in a #Google blog post.
This is what I was working on as my last project: I owned the server-side code ( #Rust running inside a C++ server on #Borg) and I was responsible for designing and implementing the identity provider used on both client and server.
You will find the latest MLS-RCS spec here: https://www.gsma.com/solutions-and-impact/technologies/networks/wp-content/uploads/2025/08/RCC.16-v2.0.pdf – and I'm looking forward to when my code comes to a phone near you 😄
All settled ! Finished my slides and polished my talk on #MLS on the #MatrixConf !
Curious ? It'll be tomorrow's first talk in the Lynn Conway room at 11.20 a.m. !
See you there !
https://cfp.2025.matrix.org/matrix-conf-2025/talk/review/R87KQCS9UCT7ML8QMTNDCLBTAAYA3B8A
