nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3vamnwvaz7tmzv4mx7tnwdaehgu339e3k7mf0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qpq0npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qf04dgf blowater--5-0-0.deno.dev is already somewhat usable. DM works for sure. Need to improve Kind-1 and UX.
But I believe it's a good starting point to use a dedicated relay for relevant topics and DMs.
Nice, I took a (really quick) look. I'm interested in the chat rooms.. do you have an opinion on the nip-87 (draft)? What capabilities will the chat rooms have? Are they just regular nostr chat channels with auth? Apologies if too many questions. 😎⛱️. Feel free to ignore or hit me on the private chats.
Not specific to NIP-87, but
1. Fully decentralized encrypted chat rooms is impossible because relays npubs are not guaranteed to have common relays. Not guarantee of relay synchronization among themselves is both a shortcoming and advantage of Nostr design.
2. It’s better to join define a single relay for a specific room. Then, we can either have fully encrypted chat or relay aided authorization. Maybe both.
Going fully encrypted, including meta data about the chat, is very challenging in client engineering. Because it gives up all the filtering capabilities of the relay. I wasted too much time last year trying to achieve this goal, sacrificing product development speed. I believe it’s possible, just too early for me.
Sorry to chime in … but I think private fully encrypted chat on dedicated relay(s) should not be a problem. This is the winning architecture that works, and we should implement clients accordingly. No?
Yes, on dedicated relay(s) will work. This is what I plan to do. I gave up on random relays.
