this post was submitted on 11 Jun 2023
116 points (100.0% liked)

Lemmy

12443 readers
64 users here now

Everything about Lemmy; bugs, gripes, praises, and advocacy.

For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.

founded 4 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] SnekInTheShell@infosec.pub 24 points 1 year ago (2 children)

For other users just be aware vote count can vary based on the instance you're on and where the post is. For example, with this post in the image I only see it has ~300 but if I view it on its origin instance lemmy.ml I can see the ~1k count. Similar things happen with other Fediverse services like Mastodon with favorites/boosts.

Just pointing this out as it isn't obvious and helps put less focus on these things when viewing content not from your own instance.

[–] Illecors@lemmy.cafe 4 points 1 year ago

I have noticed that I get the correct vote balance if I interact with it from my instance - ie upvote/downvote. Feels like a bug that will get sorted over time.

[–] pitninja@lemmy.ml 3 points 1 year ago (1 children)

That's interesting. I'm guessing here, but is that because votes from blocked servers aren't federated? I feel like having different vote totals depending on which server you're on is a little strange, but maybe it makes sense 🤷

[–] yelgo@lemmy.ca 5 points 1 year ago* (last edited 1 year ago)

Could be that blocked servers aren't feeding their votes back, but also lemmy instances (and fediverse platforms in general) don't sync data directly. Instead they all store local copies of posts and comments from various instances.

So when you upvote a post on an instance that isn't your home instance, your home instance updates the vote count for the post in its own database, not in the database of the instance the post is on.

For your vote to be counted on the other instance, your instance has to syncronize its database with the other one. And this is true for all instances. As such, vote counts on a post can be inaccurate across various lemmy instances depending on how recently any given instance has syncronized its database with the rest of the instances.