Same post, different clients. Sizeable discrepancy in the engagement and zap data

Reply to this note

Please Login to reply.

Discussion

Yep. I found the issue to be a relay discrepancy not a client issue. Hope this helps

Confirming this πŸ’œ is a Amethyst v Damus comparison?

And no difference in the relays you are using?

I should have stated which clients. It’s Snort and Damus. Snort with the higher numbers

Thanks πŸ™ for following up.

Snort has never seemed to work well with my laptop. Might be too old?

Any suggestions welcomed πŸ™βš‘οΈπŸ€™.

I do most of my posts from Damus. Haven’t found a compatible desktop app though I use Snort when on laptop

I always pull from Nostr.band as it appears to be the most accurate in combining all relays.

Yep, just ran it through Nostr.Band and it’s higher than the other two.

Going to add their relay. Currently free too.

zap n like data comes from live relays at the time - clients get relaylist bound to ur profile unless u viewing using another npub or client choose own relaylist

Adding Nostr.Band relay fixed it

nice - some has relay aggregators service maybe ( nost.band primal coracle) that collect from all public relays.