#[0]​ the purplepag.es relay is cool. I was looking for the code because I wanted to make a little bot that crawled relays looking for delete events then blasted them out to open relays. Based on my own experience needing to do that when I posted a delete event. I know there several nostr crawlers but since I quite like your NDK I thought your stuff would be a good place to start.

You mentioned in purplepag.es that you thought about doing a DHT. I also thought the same thing for NIP-65 relay list events. Perhaps we could do a hybrid. Have easy to use relays for lookup, that way you can add it to any nostr app and it just works, but on the backend have multiple light relays pull from and push to a DHT. Then if clients wanted to, they could pull from and push their nip-65 there. But it wouldn’t be needed, because you could use one of the relays.

Sharing the events via a DHT should prevent centralization around this service.

Thoughts?

Reply to this note

Please Login to reply.

Discussion

I like the idea of having relays just for specific event kinds.

I also imagine the opposite of a delete event blaster is possible: a delete disrespector bot that just blasts the original message once a delete event is seen 🤣

Cool stuff!

🤣

I like the idea of starting with DHT access on the 'discovery' relays, not clients. I'd also suggest to reuse bittorrent DHT for that (if that wasn't implied) http://bittorrent.org/beps/bep_0044.html

Webtorrent.io DHT is also pretty good and mature.