ok I finally managed to be able to query from relays recent events and store that into a DB

I'm yet to figure out how to do some clean up but one of the things that I feel is missing is to have some helpful tools to indicate what are the relays that are best for you to connect

I used to go to nostr.watch for instance and connect to some based on latency or on the name but that can be tricky.. look at what happens with this one that has "latam" so I felt may have some local content from the region but it seems it's full of spam instead?

Reply to this note

Please Login to reply.

Discussion

I don't understand, zapped instead

Asia invented spam

a key part of the solution seems to be a global list to find any npub and one relay it uses, maybe using a dht

if we can find any npubs events by knowing one of their relays then replies and boosts should handle the rest of the distribution, we can each then probably significantly reduce the amount of relays we write to, which should reduce platform load