On mobile, with Tor. 
Discussion
Does this fuck battery life?
Thereβs 900 relays on Nostr?
Actual number is over 10 thousand i saw somewhere.
Someone shared a website with a heat map of nostr relays I wish I could remember what it was called
Some men will connect to nearly 1000 relays instead of implementing a GIF button.
I wouldnt keep that phone in my pocket. Set the device down and back up lol
Where can I find a list of 1000 relays
Start with an npub that has a large follow list. Query its follow list (Kind 3), and for each pubkey in the list, query its Relay List Metadata (Kind 10002). Then, recursively repeat this for followers of followers, and if you're brave enough, go for level 3 as well. As you traverse the graph, store all relays from Kind 10002 in a set. Youβll end up with well over 1,000 entries in this set. Although youβll find a lot (and I mean a lot) of junk. Clean up the URLs, test the relays, and Bob's your uncle.
Yep, that's basically what we are doing. You can start with the users own relays. You can also use relay hints from all events to get more relays to check. Then you need to send the onion addresses via Tor and remove the local relays. Then download everybody's list and store to assemble the feeds.
Cool. Thanks π
nostr.watch
My god!
926 relays for 800 follows. i even pruned inactive. dis is not how i thought outbox would be π
I think I will remove the ones with /something after the domain. They never do anything anyway.
nostr:npub1utx00neqgqln72j22kej3ux7803c2k986henvvha4thuwfkper4s7r50e8 will hate that π
sir this is not outbox this is just connect to every relay in the world
Technically it connects only to the relays that your follows use :)
did u figure out why my 800 follows created a set of 932 relays by chance? havent been able to check on my follows in a while im graduated to following relays now ποΈ
just scrape your relays for relay relay lists, and collect the unique ones. nearing 1000 seems like a reasonable estimate of the number of relays in operation now
i may do this to regain some sanity.. or loose some..
Just Unique makes you miss most content as people's posts are not in all their outbox/inbox relays.
in my relay #orly there is a spider that, based on the first and second degree follows of the designated owner npubs can fetch all the events of first and/or second degree, and it can either just grab the stuff that helps you find people (relay lists, profiles, follows/mutes) or it can just scrape for them. i didn't make it automatically use the relay lists it has in the db to keep it simple but it would be simple to add that.
if you paid for one relay, and every 10 minutes it was fetching events from everywhere, a) it would be worth paying for and b) everyone would find everything.
but it requires auth to really work.
also for relays operators to be able to easily contact other relay operators to make peering arrangements
That's a user's problem. If they're using an outbox that does not accept their notes or does not have them all, you're just kicking the problem down the road for them. That's why they should pick 3, and make sure those 3 relays have their events (not just be all lossy, with no retries etc).
EG: If someone has damus in their relay list, but they don't post there half the time. Sorry they're invisible now. They gotta pick relays wisely. There should also be a relay list, for umbrels, and filters and etc, get that crap out of nip65.
Anyway, I ran a quick analysis on my follows relays, only NIP65 (not kind3), and normalizing case and trailing slash:
Calculating optimal relay set using greedy algorithm...
Total follows with relay lists: 726
Greedy set cover algorithm:
============================
1. wss://relay.damus.io (+485 follows, 66.8% total)
2. wss://nos.lol (+ 95 follows, 79.9% total)
3. wss://nostr.wine (+ 38 follows, 85.1% total)
4. wss://purplepag.es (+ 23 follows, 88.3% total)
5. wss://relay.mostr.pub (+ 13 follows, 90.1% total)
6. wss://wot.utxo.one (+ 7 follows, 91.0% total)
7. wss://theforest.nostr1.com (+ 5 follows, 91.7% total)
8. wss://premium.primal.net (+ 4 follows, 92.3% total)
9. wss://bitcoiner.social (+ 2 follows, 92.6% total)
10. wss://creatr.nostr.wine (+ 2 follows, 92.8% total)
11. wss://filter.nostr.wine (+ 2 follows, 93.1% total)
12. wss://inbox.relays.land (+ 2 follows, 93.4% total)
13. wss://nostr.mom (+ 2 follows, 93.7% total)
14. wss://nostr-pub.wellorder.net (+ 2 follows, 93.9% total)
15. ws://4bluxabinr4kyukywrhkgxaqppbqo6hh6zb5z42h7kdoqkju4jbqq3id.onion:4869 (+ 1 follows, 94.1% total)
16. wss://37.202.159.214:4869 (+ 1 follows, 94.2% total)
17. wss://auth.nostr1.com (+ 1 follows, 94.4% total)
18. wss://bostr.bitcointxoko.com (+ 1 follows, 94.5% total)
19. wss://cfrelay.puhcho.workers.dev (+ 1 follows, 94.6% total)
20. wss://fragarach.nostr1.com (+ 1 follows, 94.8% total)
Optimal relay set covers 688/726 follows (94.8%)
Uncovered follows: 38
I'd do a method with at least 3 active relays for each follow since from time to time relays go off-line. Overtime, people should migrate to outbox with just 3 relays in their lists anyway.
But I am way more interested in getting personal relays for each follow. I don't think 1000 relay connection is a big deal. Phones can handle much more than that.
Right, and also yeah nip65 has become polluted by all these blastr/proxy maxis. It's being used for purposes it was not supposed to be used for. Clients forced everyone to override the settings, by not providing fine tuned relay types like amethyst is going to..
Glad to see you're on it. :shipit:
this is neat, need more of this
Each follow has 5+ relays.. so..
Also lots of relay variants, like filter.nostr.wine/npub...
and.... why not!? "they say: it can handle that"
You will break Haven's Inbox and chat relays if you do this (although chat relay shouldn't be in kind 10002 to begin with).
The best way (i think) would be, query nip66 for these relays. if they dont have a nip66 that is online, purge them from the list.
IE: there are two relays fully dedicated to NIP66 data that I know of. They are: wss://monitorlizard.nostr1.com (me) and wss://relaypag.es (nostr watch)
The monitors concept is interesting too, as anyone can run a monitor. It's just a pubkey, that if a user wanted to, they can subscribe to a set of these monitors by pubkey as well.
Amethyst could spread these events around more if you want more decentralization, currently, I'm not sure where all you can find them besides these relays.
Anyway, just another nip66 post. Eventually someone will use it (jumble does!) because it's awesome and solves a lot of relay problems. (Like geo / feature discovery). In this case, you could use it for liveness check without having to connect to the relay at all.
amethyst users could be monitors themselves, cache some of it locally for startup, publish their results for others that follow them or etc.. lots of possibilities. it only needs to check once a day or etc to be effective in getting rid of ded relays.
Frankly the dead relays aren't much of an issue since we only try to connect from time to time, with progressively longer delays. The real issue are the duplicated or buggy ones because it makes the app download things twice or three times.
ohh, ok. i assumed de-dupe would be easy. but yeah I imagine my follow list has a lot of wine filter subscribers if that is all this is.. π€
As you have your picture and your real name here, Tor ia senseless.