catusr

View original page

@catusr@catodon.rocks · Joined ⁨May⁩ ⁨2026⁩

nothing to see here

9Posts
0Following0Followers
catusr@catusr@catodon.rocks

Replying to @⁨lnkr⁩

@lnkr@staging3.plamenu.com @panos It seems that emmisary implementation is indeed a client with the client owning the MLS cryptographic state. https://github.com/EmissarySocial/conversations-mls/tree/main/user-conversations/resources/app

MLS-encrypted conversations template for Emissary. Contribute to EmissarySocial/conversations-mls development by creating an account on GitHub.GitHubconversations-mls/user-conversations/resources/app at main · EmissarySocial/conversations-mlsMLS-encrypted conversations template for Emissary. Contribute to EmissarySocial/conversations-mls development by creating an account on GitHub.
catusr@catusr@catodon.rocks

Replying to @⁨panos@catodon.rocks⁩

@panos @catodon So, basically you are going to support E2E messages based on current specs, because both emmisary ( https://github.com/EmissarySocial/conversations-mls/commits/main/ ) and bonfire ( https://github.com/bonfire-networks/bonfire-app/issues/1701 ) have their last activity regarding E2E messages in July.

MLS-encrypted conversations template for Emissary. Contribute to EmissarySocial/conversations-mls development by creating an account on GitHub.GitHubCommits · EmissarySocial/conversations-mlsMLS-encrypted conversations template for Emissary. Contribute to EmissarySocial/conversations-mls development by creating an account on GitHub.