• SnekInTheShell@infosec.pub
    link
    fedilink
    English
    arrow-up
    24
    ·
    1 year ago

    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.

    • pitninja@lemmy.ml
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      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 🤷

      • ErzatzCadillac@lemmy.ca
        link
        fedilink
        English
        arrow-up
        5
        ·
        edit-2
        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.

    • Illecors@lemmy.cafe
      link
      fedilink
      English
      arrow-up
      3
      ·
      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.