Oddbean new post about login | logout nostr:nprofile1qyd8wumn8ghj7urewfsk66ty9enxjct5dfskvtnrdakj7qghwaehxw309an8yetwwvhxummnw3erztnrdakj7qgcwaehxw309anxjmr5v4ezumn0wd68ytnhd9hx2tcppemhxue69uhkummn9ekx7mp0qyt8wumn8ghj7emjv4jkuum0w4kzuumsv93k2tcqypl62m6ad932k83u6sjwwkxrqq4cve0hkrvdem5la83g34m4rtqegk5xps3 I'm woth Niel on this one, will shortly be releasing a client that does relay based groups without nip 29.
What are the events kinds and spec behind the chat messages in a space (i.e. relay)?
WIP here: https://github.com/coracle-social/nips/blob/relay-chat/xx.md Very WIP
¡Muchas Gracias!
after reading Niel's article and https://github.com/nostr-protocol/nips/pull/1495 I tend to agree with your points, ideally we have simple groups without the need for explicit support from relays or introducing redundant kinds. I will keep an eye on your feeds since I'm also working on this type of client.
I am on a similar page to neil and hodlbod on this one. I think groups or communities can be done with 'regular' relays with auth (arguably already is being done).. nip29 from my perspective has relay side complication, and its unclear to me that what it accomplishes is any different than using a different kind# so regular clients dont repost those notes. super excited to hear about new clients coming up!! 🎉 i will do everything i can to support them. this is why i pushed hard to get auth going, it seemed to be a missing piece of the puzzle for more community, & dms .. if nip29 does gain traction/adoption/demand i will re-assess priorities for relay.tools at that time.
Awesome, excited to hear it. By the way, I am no longer working on reconciling nip 29 with relay-based groups, instead I'm creating a new NIP that will hopefully serve the purpose: https://github.com/coracle-social/nips/blob/relay-chat/xx.md. The NIP is very much a WIP, lots of the hard problems with detecting relay membership still need to be solved. If you're interested in pooling resources, my client is here: https://github.com/coracle-social/flotilla