in actual fact, none of the chat protocols have solved any problems. the biggest reason to update to marmot MLS is it's a unified DM/group chat. at all times, forever, and from the beginning, AUTH has always been the thing that provides metadata security. you only have to read the architecture of matrix, signal, and the rest, to understand this. but even today, we here this "we don't go to ravenholm" meme about nostr DMs and you are not thinking bro. not thinking Auth is what makes privacy metadata security possible. you can get an answer to that question in 5 seconds with any LLM. do yourself a favor and stop making yourself sound like a stupid person to anyone who understands distributed systems and security

Replies (8)

Have you seen the latest papers on all the MLS vulnerabilities AI is finding? The thing is too big. So difficult that many folks outside Nostr are giving up on it and starting new protocols. I don't mind using Marmot, but it has been under development for over 2 years and it's still not stable or even usable.
Alan's avatar
Alan 3 months ago
I have it working with my chatbot pretty reliability, and I built it from a simple vibecoding session with no experience vibecoding. I am an ex software dev. I find that hard to believe.
Alan's avatar
Alan 3 months ago
It wouldn't work unless White Noise supported adding users to an existing group. Pika supports this today, White Noise tomorrow. That isn't a problem with the protocol. The issue is with nuance between implementation details.
Reference Implementations.. they are way too big.. the original idea of hatcheting in tree branches is good. The implementation of the things that idea needs to have in place to run correctly is where all the problems and attacking possibilities lie. I don't think they are new problems, it's just that AI can be more effective in finding and exploring them inside codebases.