Fork Flotilla and implement. We've been using it as a workspace for #PodSystems for like 8-9 months now
Discussion
I have zero experience with Flotilla
It's basically a Discord clone for Nostr. Solid potenial and already highly usable.
is flotilla still working ok with relay tools? i know i still haven't supported nip29 but I assume that you found a way 😅
NIP29 support would be amazing to add. We kind of just settled into living with everything in one chat feed 🤣and need to make use of threads more. Notifications are better but not consistent among users so we've been regularly testing other options. Also been eyeing the #Budabit fork lately with their git functionality 👀 But, in short relaytools is working and we use it although it's probably not the ideal setup anymore with how Flotilla has grown.
tbh, NIP29 support would escalate our timeline on a migration off Telegram for our backups 😅
nostr:npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5h how much of a lift would it be to add nip29 support in relaytools? 😅
depends.. a lot of the time factor in implenenting it is just the risk factor (IE, integration testing and or finding that some solutions may just not work as advertised). So by risk I mean that, a lot of time may be spent going in a direction that wasn't going to work or could incur unknown integration debt.
https://habla.news/u/hodlbod@coracle.social/1741286140797
https://github.com/coracle-social/frith/blob/master/go.mod is the only relay implementation that already says it supports, but is on a now depricated version of khatru library.
Gotcha! Makes sense.
I wonder if a simple agent type thing (a bot with keys), separate from the relay itself would be able to do the nip29.. Things like this, should probably be investigated.. 🐳
I would likely try to either add the functionality to 1) strfry proxy, 2) a bot, or 3) integrate with a relay that provides nip29 and can run without locking up. (not necessarily in this order).