Replying to Avatar pam

Hi #[5] primal.net looks great! From your explanation, clients tend to aggregate the followers wrongly and that that actual amount of followers is larger #[7]

However, from #[6] 's explanation, this is dependent on the relay set limit #[8]

How is your calculation different on primal, and how you do get past the relay limitations ?
Avatar
miljan 2y ago

Hey Pam, Mazin's explanation is excellent and it is aligned with my view. Standard Nostr clients attempt to get follower counts directly from the relays, so they are limited by two things: 1. the relay set that the user is connected to; and 2. the max number of events that a relay will return per request.

Primal uses a caching service with aggregation capabilities, similar to nostr.band and nostrgram.co (and maybe others?). We aggregate all events from all public relays, therefore our follower count calculation is not subject to the limitation mentioned above.

You can read more about our approach here:

https://habla.news/a/naddr1qqd5c6t8dp6xu6twvukkvctnwss92jfqvehhygzwdaehguszyrtp7w79k045gq80mtnpdxjuzl9t7vjxk52rv80f888y5xsd5mh55qcyqqq823cf39s98

Reply to this note

Please Login to reply.

Discussion

Avatar
pam 2y ago

I asked a similar question to primal.net developer, Miljan as their caching method of finding followers is similar to nostr.band, and yet it is diff from how other clients count, as each relay is limited by the stored events. This was the response, and has a blog link as well for more info

#[2]