XD fml

Papi https://music.youtube.com/watch?v=XjkEs_AGnuU

https://music.youtube.com/watch?v=Fr_3GsSrk1A

GM

GM 🌞

You're in

Is the spec open?

Join the party, we are already almost 20 people 🔥

Yes, which also decouples the service and the visibility of the user. The relay just transmit ephemeral messages that doesn't reveal nothing useful by itself but can see the client ip, the service just subscribes to the relay with filters that doesn't reveal too much by themselves and cannot see the ip of the user. Plus deferring these makes deployment automatically easy for anyone, even from the wifi of a coffee shop. We are just exploring this model with cvm and cordn. Trying to choose the right tradeoffs

Yes, but that makes deployment dependent on ips, dns, nats etc. With cvm you remove all that and don't need to deal with networking to deploy anything

Check https://cordn.net

Not exactly. It uses a coordinator where messages are stored so async comms can happen. The coordinator is a cvm server ( which is basically rpc over nostr contextvm.org ) so relays are just uses as an ephemeral bus for commands/messages. All messages are ephemeral and encrypted so the identity of the sender, receiver or even the cordn being used is totally obfuscated across other cvm traffic. Also coordinators are as dumb as relays and learns nothing (almost, nothing insightful in any case), and ofc you can deploy your own coordinator easily for maximum privacy/sovereignty