• FaceDeer@fedia.io
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    11 hours ago

    As I understand it, you can downvote the content posted by instances that don’t support downvoting, they just don’t see it over there and can’t add downvotes of their own when using that instance.

    In a similar way I could make my own instance that implemented “sidevoting” alongside up/down, people could vote left and right on those posts and comments, and the rest of the Fediverse would be blissfully unaware of the nonsense going on over on my instance.

    • MagicShel@lemmy.zip
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      10 hours ago

      I think based on the second part of your post you know this, but I’ll elaborate based on the first part:

      I would think it goes slightly further. Let’s posit:
      server-A: poster / does not support DV
      server-B: Bob, Jim, Joe / supports DV
      server-C: Sue, Ann, Kat / supports DV

      Server-A is the system of record for post P.

      Bob, Jim and Sue all downvote the post.
      Joe, Ann and Kat all upvote the post.
      All servers federate.

      Poster sees: 3UP
      Anyone on server-B sees: 2DN, 3UP
      Anyone on server-C sees: 1DN, 3UP

      I believe this is how it works. The upvotes federate across all instances and are seen by everyone. The downvotes do NOT federate to the home instance, and so they do not federate out to other instances. The downvote total you see for a post only includes voters on your own instance.

      I have not studied the code or architecture so I could be wrong, but I think this is accurate.

      • FaceDeer@fedia.io
        link
        fedilink
        arrow-up
        3
        ·
        10 hours ago

        Yeah, I think that caveat applies, with the same disclaimer for me; I haven’t studied the code or architecture in detail, I’m just going off a high-level understanding of how this works. The “server of record” is the server that re-broadcasts everything to those that federate with it so it can act as a filter.

        ActivityPub is a nice idea, but I can imagine some manipulative shenanigans an instance could get up to with this kind of setup. I hope there are mechanisms for detecting that sort of thing.