It’s over 30, actually, but doesn’t really matter. Of course it is not going to be perfect coverage, even if you add every known online relay because some will rate limit your REQs or reject your filters, some will require AUTH, etc. Our goal is to have very good coverage, not perfect - and we have achieved that for multiple years.

Event propagation on nostr is way more broad than people realize. Most events end up on the top 10 relays within a few minutes of being delivered, even if they are not sent to one of them directly.

Reply to this note

Please Login to reply.

Discussion

That's fair, I don't have the numbers so I trust you on that.

Since I'm AUTHed and you have my contact list, if people I follow have outbox set up (i.e. their 10002 points to where they write) - do you go fetch notes there? Or not at all?

AUTH is not transitive and is tied to only one relay, you would need signer connect for that.

I don't think you understood what I said. Forget AUTH, you know who your customers are. If so, you can fetch their contact lists, so you are able to look at all their contacts' 10002 events and pull from those relays

Ah. In my case I’m considering directly indexing those relays fully, as it would be more efficient + faster than forwarding REQs based on AUTH

signer connect is a thing? like ssh-agent forwarding?

Standard nsecBunker stuff.

No - filter only respects NIP-65 for broadcasting, not for reading.

"Your events are automatically broadcasted to your first 4 "write" relays and the first 4 "read" relays from the first 5 tagged users.”

Got it, that's how it works today. But do you plan to support what I suggest? or why not?

We can just ingress from all the online relays if it makes everyone happy - it’s a simple change on our side.

Easier than trying to be precise for no real gain I think.