It is predefined and changes according to the developers' criteria. You can find info here:

https://nostr-wine.github.io/filter-relay/

Reply to this note

Please Login to reply.

Discussion

Thank you 🙏⚡️

Hm, my follower count drops by more than a thousand if I replace the list of pub relays with filter.nostr.wine.

Something doesn’t work 🤔

Re-adding them gets it back up. Something doesn’t work as promised by nostr.wine I guess

You must also add relay.nostr.band to complement filter.nostr.wine, in case I get all the followers.

I did but once I remove relay.current.fyi and nostr.oxtr.dev I lose more than thousands of followers

#[3]​ What could be happening? Could it be the client used? In my case I keep practically all the followers and the relays mentioned by the colleague are in the reading list.

When I wake up a bit more I’ll try to find one of my hundred posts about follower count.

tldr it’s a garbage number and you’ll get a different answer each client you calculate it on with the same relays. Moreover with some clients you’ll get a different number each time you click it.

As long as you are writing to and reading from the same places, you have the same reach.

We are NOT currently writing to relay.curent.fyi as they had changed some configuration that was causing issues.

I reached out to them but communication has been slow. With that being said I’d find it hard to believe you have many followers that ONLY share that one relay in common.

I deleted and added all the relays in your list one by one to check it. Just telling what I experienced.

There’s a good obvious explanation I just need to put it in words.

It has to do with event limits per relay. If you are only querying one you’re capped by our max events we will return per request.

Thanks for putting in the effort. Looking forward to the detailed explanation 💜

I have a more detailed/correct response that I’ll write up shortly and link here.

Thank you 💜

Tipp: I use NostrGram for checking followers. (Clients can show different count)

Technically you don’t loose anyone. They will see your posts because they are podcasted to the relays that they added through your “proxy” relay.

You might not see them as followers in your client though, because the info didn’t get pushed to the relay u are using. (If I understood that correctly).

Thanks, but I know that I don’t really lose followers. Still, it is a good indicator about your current reach. If I pull all the contact lists from my currently connected relays and it’s 1000 people less then before, then also the reach of my notes is 1000 people less

Well no. I don’t think so, if u use relays that act as a proxy (Nostr.wine filter) and repost your notes to the free relays. Your followers then see your posts, because on there side they are still following you.

That doesn’t make sense at all. So the proxy is only used for notes but not contact lists? Explain me why Cyph3rp9nk has all his followers but not me

The proxy is also used for contacts in the case of filter.nostr.wine, in fact you can test it by putting only that relay and you will get many contacts.

relay.nostr.band also acts as a proxy and gets contacts but it limits the query.

Sorry I meant for followers

Yes that’s what I thought so what Kevin is saying makes no sense

I’m sorry. I am also still learning. Just trying to make sense of it all.

No worries, maybe I am also wrong. Discussions like this help to understand 💜

Cyph3rp9nk asked the creator. Lets see what he is going to reply. Thanks anyway 🙏

Yes. Many contacts but sometimes not all right? So why is that? Do the relays, that have the info, not share it?

Well one side is posting notes (push side). In the example the paid proxy relay pushes your note to all the relays on its list.

Your followers now see it. (On there relays they are following you.)

The other side: the pull information from relays depends on the client and the relay u are using.

If I understand it correctly: when u follow a new account then this info get stored on the notes u are connected to in this moment. I think the problem lies in the sharing of the contact lists. But maybe we should ask someone from the devs for this one.