• SorteKaninA
    link
    fedilink
    English
    arrow-up
    11
    ·
    4 months ago

    The underlying protocol, ActivityPub has no support for aggregated votes.

    if a federated server acts up and sends bad vote totals, the instance could be blocked for it as a trade off.

    How would you detect this? It seems very hard.

    • Pichu0102@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      4 months ago

      Vibes, generally. If you see a server regularly having lots of downvotes or upvotes on things that otherwise would go the other way, it’s probably a bad sign and asking the other instance admin what’s going on should be a way to start figuring out how to handle it. As for activitypub, there isn’t a generic server to server message that could contain a VoteTotals field while updates to the standard are proposed for addition?

      • SorteKaninA
        link
        fedilink
        English
        arrow-up
        4
        ·
        4 months ago

        I don’t think vibes is good enough. There’s not enough certainty there. You could ask the other instance admin, but who’s to say that admin is cooperative? They could be actively malicious and hiding behind this mechanism. You would ask them what’s going on and they’d just say “nothing bad to see here” and you would have no way to disprove that.

        As for activitypub, there isn’t a generic server to server message that could contain a VoteTotals field while updates to the standard are proposed for addition?

        There is no such thing at the moment, though Lemmy could in theory implement it among its own instances, though even that would be hard. But it would be very non-standard and wouldn’t work with other ActivityPub implementations.