Mazin on Nostr: Yup! Exactly what Cameri said. If you’re curious how follows counting works you can ...

Yup! Exactly what Cameri said. If you’re curious how follows counting works you can checkout this note:

quoting nevent1q…z2ax

I got asked about follower count again today. Why does my follower count go down when I delete public relays (in our list) and replace them with filter.nostr.wine?

I’ll give you one final explanation to rule them all. First, let’s go over how clients calculate your follower count.

1. Your client sends a request to all your connected relays asking for accounts who follow you
2. Relays answer back with the events requested
3. The client aggregates the event total and displays it

Each relay has a set limit on how many stored events it will return per request. For some relays it’s 500, others 1000, some as high as 5000. Let’s say for simplicity that all your public relays use 500 as their limit. If you ask 10 relays for your followers the max possible answer you can get is 5000. That won’t change if you have 20,000 followers or 100,000. You may get back a “different” 5000 each time, but you’ll still cap out at 5000 because that is the most events your client will receive.

Our limit on filter.nostr.wine is 2000 events. If you replace 10 public relays with only filter.nostr.wine, the MOST followers you will ever get back from our filter relay is 2000. That doesn’t mean you only have 2000 followers or that your reach is reduced in any way.

As long as you are writing to and reading from the same public relays, neither your reach nor any content was lost. That concludes my TED talk. I hope you all have a fantastic day and weekend.

Nostr.wine currently limits max tags per event to 2000, so following over 2000 people will result in your “new” kind 3 event not being stored correctly. I’m open to increasing this limit but it might have performance implications.