https://video.nostr.build/48bc525bb30a1a9de627a30a974dfa733f9677a97c14bb6912d67504b89cec90.mp4

Building support for NIP 29 while keeping my vision for flotilla intact wasn't easy, due to some assumptions relay29 makes about implementations. Thanks to nostr:nprofile1qyd8wumn8ghj7urewfsk66ty9enxjct5dfskvtnrdakj7qgmwaehxw309aex2mrp0yh8wetnw3jhymnzw33jucm0d5hszymhwden5te0wahhgtn4w3ux7tn0dejj7qpq80cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsh4nk43 for working with me to adapt the spec and relay implementation so that they can work for me. The necessary changes were much smaller than I anticipated.

I still have a lot of questions about how telegram-like ("pure") NIP 29 clients will work with discord-like clients like flotilla, especially from users' perspective. Currently, the groups.0xchat.com space looks like a junkyard in flotilla, because I encourage community organizers to host their own relays, and therefore treat groups as loosely related, while 0xchat is open for anyone to create a group.

For that reason, I think there will be some divergence between the different types of clients on which relays are preferred. It won't make much sense to use flotilla for groups created in other nip 29 clients, but it may make plenty of sense to use 0xchat for groups created in flotilla (if for example you only want to be in a single room for a space). It will be interesting to see how this evolves.

If you haven't already (or even if you have), give it a try at flotilla.social. And if you're a community organizer, I'd love to hear from you so I can make the software work better.