mleku on Nostr: it shouldn't be difficult to add this feature as a background process/sprocket the ...
it shouldn't be difficult to add this feature as a background process/sprocket
the directory spider i added to #realy scrapes relay URLs from the database and then randomly tries their nip-11 first, to find relays that probably have sane behaviours
if they require auth, you can set an nsec for it to use...
it's a very slow and cautious spider, the data it seeks is not a big set (the directory event kinds i keep talking about)
opening up big wide connections to subscribe/scrape relays is also possible, so you can even pull in events reverse-blastr style, i've written one of these things ages ago for my paid gig (arweave social aggregator with blu esky and fartcaster as well) and pippellia (npub176p…vgup) has been writing something in his "crawler" that does similar things but focuses mainly on follow (and maybe mute? i didn't read real close the filters) and it builds a graph model out of it and has a walker that measures distances between nodes
the directory spider i added to #realy scrapes relay URLs from the database and then randomly tries their nip-11 first, to find relays that probably have sane behaviours
if they require auth, you can set an nsec for it to use...
it's a very slow and cautious spider, the data it seeks is not a big set (the directory event kinds i keep talking about)
opening up big wide connections to subscribe/scrape relays is also possible, so you can even pull in events reverse-blastr style, i've written one of these things ages ago for my paid gig (arweave social aggregator with blu esky and fartcaster as well) and pippellia (npub176p…vgup) has been writing something in his "crawler" that does similar things but focuses mainly on follow (and maybe mute? i didn't read real close the filters) and it builds a graph model out of it and has a walker that measures distances between nodes