Oddbean new post about | logout
 nip-29 groups or relays as communities 🤔 why not both?

https://image.nostr.build/7d06914c3b3557ecdde395fb6b250fd84404f070f5ffaea5e4ddf6f6af815aee.png https://image.nostr.build/45d560beab6a0fe1c50388dcd0d6190f551d58d4a469b5dbc31a2240361cf16a.png 

 
 I was tinkering around with the same this morning

Trying out the invites for a nip29 group using 0xchat

nostr:naddr1qpqrjef4xsmrgdpnxvmnje3kxyengvfsxpskywf3x93rydf389jrgwp4xv6nwctrxv6r2vps8qunwvr9x5engcf5vyerxwpjvymrxc34xqq3camnwvaz7tmjv4kxz7fwvaex7atswvhxu6tsxgujucm0d5pzqpnrnguxe8qszsshvgkvhn6qjzxy7xsvx03rlrtddr62haj4lrm3qvzqqqyctqqzq8mm 
 sweet! I gotta render these group metadata events in chat so you can share groups. 
 This looks awesome. I am thinking on these lines for Fishburners startup community. I wonder. 

Could it handle one relay with multiple NIP-29 groups inside? 

Trying to figure out the recipe book! 
 Hey Rod! Yeah a NIP-29 relay can handle multiple communities, the wss://groups.0xchat.com relay has more than a hundred! 
 Thanks! For clarity I was mostly thinking about the UI pattern in your client app. E.g. if my community currently in Slack has multiple "channels", I can replace Slack with a relay, and the channels with NIP-29 groups, but there may need a visual hierarchy of "Relay>Group" or at least a grouping of Relay1Group1,2,3,Relay2Group1,2,3, etc.

Just musing. Trying to figure out the correct pattern 
 I also thought about having the Relay > Group hierarchy but I settled on this because a relay can also be a group and a group can be migrated to another relay (no hosting lock in). Eventually I'll add direct messages too so this Telegram-like UI is the best choice imo. 
 +1 
 TY! I can't fault your thinking. And also, Telegram also has this nested pattern, see e.g. Nostr Relay Ops Collective on TG. 
 https://image.nostr.build/914f49bda24d98a166bb5dfd366eece0d587b4c4ce8d67ab9e2c312d883e563f.jpg