Replying to Avatar HiveTalk

Hi nostr:npub1n0sturny6w9zn2wwexju3m6asu7zh7jnv2jt2kx6tlmfhs7thq0qnflahe , just wanted to reach out, to see if you ran into any conclusions when you looked at making nostr:npub1z0lcg9p2v5nzg5fycxq0k56ze6snp42clmrafzqpn5w6u74v5x9q708ldk interoperable with nostr:npub1n0stur7q092gyverzc2wfc00e8egkrdnnqq3alhv7p072u89m5es5mk6h0 🐝πŸ₯°

Specially in the case of open rooms, having that kind of visibility could help people doing public events to appear in more nostriches radar. What do you think?

Any issues you anticipate or have run accross?

Cheers!

Hey last time I could not find the repository for the new HiveTalk, only the old one, but if it's using LiveKit like nests then it should be easy to add support.

Just a bit hesitant to add new interop after the last nests kind number rugging so it's a bit low priority for me now, I'll take a look again in some time.

Reply to this note

Please Login to reply.

Discussion

Thanks man, yeah it’s using livekit like nests :)

Thanks! Yeah, livekit like nostrnests

Thanks! Yeah, livekit like nostrnests so will hopefully be easy to support πŸ«‚πŸ’œπŸ

Hi nostr:nprofile1qythwumn8ghj7enpvf5kzm3wdehhxarjxyhxxmmdqyxhwumn8ghj7mn0wvhxcmmvqqsfhc97pejd8z3f488vnfwgaawcw0ptlffk9f94trd9la5mc09ms8s627z6m , I was explicitly asked by derek ross and fiatjaf to write the new Kind Number 30312 for both nests and hive and extension to NIP-53. I just want to be clear we're not "rugging" you, this was work I completed for the benefit of the community for free.

Now that nests and hive are on the same standard all you have to do is just change the number from 30311 to 30312, that was the only major change. you can also find the hive events broadcast by using nak. No need to read the source code, all the data is on the relays publically.

example:

$ nak req -k 30312 --limit 2 wss://hivetalk.nostr1.com

[ or use wss://relay.damus.io or primal or nos.lol ]

We also gave months notice in advance too. It wasn't a rug. It was to make dad happy.