If I only download from nostr band, I'm missing a bunch of notes in the feed. So this isn't a standalone download proxy?
Discussion
As I explained to a colleague I am not sure from which relays relay.nostr.band collects the information, its author says from all of them but I cannot verify it.
In my case the combination of relay.nostr.band together with filter.nostr.wine gives me practically all the followers.
At the moment I don't know any relay that allows the reading of "all" in the same way that nostr.mutinywallet.como does with the writing. In this case if I have been able to verify its code and what it does is to read the api of nostr.watch of relays online and to write in all of them.
When reply to an event is posted most clients include the source relay in the reply (relay of event to which you're replying). So by reading from one relay you eventually learn about other relays, when users interact with them. That's what my server does. As soon as it discovers a new relay it starts reading from it and expands it's network. Right now the number of active relays I read from is 1126 (at the bottom of https://stats.nostr.band/).
But, it doesn't mean that I will _serve_ all events from all relays to clients. 70% of all events published on big public relays is spam, which I filter. Sometimes there might be false-positives. So it's probably not about 'which relays I'm reading from', but 'was that event spam filtered'.
#[3]
I forgot this detail, relay.nostr.band seems to have a limit in the contact query, that's why I use it as a complement of filter.nostr.wine, however it seems to read all the events.
Not sure what limit you mean. All relays limit the number of evens they could return in 1 request, all clients know how to request the next batch to consume everything that relay has.
If I only attach your relay, my number of followers goes up to 1000 and it doesn't go beyond that, that's why I assumed that the query from your relay had some limit.
Which client are you using?
Damus, but it only affects the follower count, I have been able to verify that if it serves events of all the followers.
Well I guess Damus doesn't bother paging through followers atm and just hopes most people have lowish number that fits relays' per-request limits.
Your data is correct, so it seems to be a problem with Damus.
Can I get data on which relays are using your relay to read?
I read from all relays. I don't know who reads from me. Whoever wants to?
Most relays don't read from anyone, they just accept events from clients. Maybe nostr.wine reads from many relays, maybe there are others - I don't know.
Perhaps I have expressed myself badly.
For example nostr.mutinywallet.com reads the nostr.watch api and writes to all relays marked as online.
In the case of filter.nostr.win the list is small, they are the ones indicated in the main post.
In the case of nostr.band I don't know where it gets the data from, i.e. which list of relays.
My relay has 1234 followers of yours, maybe your client doesn't know how to fetch them properly.