Upvotes seem to just federate as likes and dislikes.

  • schnurrito@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    23
    ·
    5 days ago

    Yes, but then you can have malicious servers sending fake numbers without other server operators being able to check whether this is at all plausible.

    (It’s still possible for malicious servers to send fake votes, but server operators can see which users they are stated to originate from, then block that server if that looks like it’s doing that. At least that is my understanding.)

    • PeriodicallyPedantic@lemmy.ca
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      2
      ·
      5 days ago

      What do you mean “send fake votes”?
      Or rather, who do you think should be responsible for identifying and blocking fraudulent votes?

      And how do you reconcile votes that come from servers that you’ve defederated with? Should everyone have the same view of the post, or should people only see votes from servers that their server is federated with? What about votes from users you’ve personally blocked? Etc

      I personally kinda think that the responsibility is on the server hosting the post, and that everyone should see the same (but anonymous) vote count, of which the hosting server is the single source of truth.

      • skulblaka
        link
        fedilink
        English
        arrow-up
        7
        ·
        5 days ago

        A malicious hosting server could use fake points to blast any message to the top of everyone’s feeds until manually banned or defederated

        • PeriodicallyPedantic@lemmy.ca
          link
          fedilink
          English
          arrow-up
          4
          ·
          4 days ago

          I’m not sure how giving every server access to the votes solves that.
          The malicious server can make fake users to pump up votes. your server admin has to notice, then check the vote logs, then see what’s happening and defederate them. That’s pretty much what you described in your scenario, anyways.

            • PeriodicallyPedantic@lemmy.ca
              link
              fedilink
              English
              arrow-up
              1
              ·
              4 days ago

              But it also has to be defended separately by the admin of every server that has a user subbed to that community. Seems like a large burden to put on small-mid instance admins.

              I’d be surprised if my server admin was really paying attention that closely to votes on communities I’m subbed to, right?
              I have to admit I don’t know the view that admins get of how their server intersects the fediverse.

        • catloaf@lemm.ee
          link
          fedilink
          English
          arrow-up
          2
          ·
          4 days ago

          Yes, that’s happened before. They were sending a very large number of votes, so it was immediately obvious. Even a couple dozen from an unknown instance will be noticed, when an admin sees it and says “huh I haven’t heard of that instance” and when they look there’s nothing there.

        • Natanael@infosec.pub
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          4 days ago

          If that’s the concern it’s better to have each server send a signed counter of votes coming from its own users to the hosting server for the post being voted on, then people can see which servers three there’s how many votes from.

          This provides the same privacy as intended before (your account host knows your votes, nobody else does) and you can see which servers are acting suspiciously while allowing everybody to get a consistent view of votes (the host simply tally up the votes from each other server, and offer up the signed counts on request)

    • Wooki@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      5 days ago

      It’s only fake numbers for posts on the instance.

      Not the first malicious instance, wont be the last.