I was trying out all the MLS+Nostr clients, but they were very unreliable, so my current mindset is - wait one year, then retry. I hope you'll all be interoperable and reliable by the time ;) It's not that I am not bullish on it, I am, it's just not my main focus now to play with these apps, but I believe you'll manage ;).

Replies (1)

Besao's avatar
Besao 2 weeks ago
Hey! Cordn main developer here. Hope you don't mind me jumping into the conversation. Well, what you're describing is exactly what led me to start working on Cordn. Before this, I was trying to implement Marmot and create my private chat app using it, but as you said, it was really unreliable to the point that it was driving me mad because I wasn't able to make it work reliably for groups of more than two people... Then I read the article gz wrote about private comms over public infrastructure and it all became clear. I also reused their ideas of an MLS coordinator over CVM, which is basically RPC over Nostr that allows for really easy deployment without needing to touch DNS, IPs, or anything similar. That was really what gave me hope that this could work, so I proceeded with it and created cordn.net, which is a web client implementing the protocol. So far, it's working great, even with large groups. MLS was designed to be used with coordinators, so we decided to go that path instead of fighting the protocol, which indeed made it reliable and more private than Marmot. Also, anyone can run their coordinator easily, etc. We're running one for bootstrapping. So please, if you feel interested, just test it at https://cordn.net