Edit: obligatory explanation (thanks mods for squaring me away)…

What you see via the UI isn’t “all that exists”. Unlike Reddit, where everything is a black box, there are a lot more eyeballs who can see “under the hood”. Any instance admin, proper or rogue, gets a ton of information that users won’t normally see. The attached example demonstrates that while users will only see upvote/downvote tallies, admins can see who actually performed those actions.

Edit: To clarify, not just YOUR instance admin gets this info. This is ANY instance admin across the Fediverse.

  • @jcg@halubilo.socialEnglish
    14•1 year ago

    Which is why either

    • Votes should be publicly viewable like they are in kbin. Not necessarily readily viewable to save server resources, but through a click through or something. No need to hide something that is, in essence, public info.
    • Votes should not be federated at all, but that would be awful for very small instances, though this is how Mastodon has always done it.
    • Votes should be federated in aggregate, but this would kind of break federation because it’s a new type of Activity.
    • @naonintendois@programming.devEnglish
      7•1 year ago

      Another option is assigning an id per user that’s only used for tracking votes. Only the user’s server would know who did the voting, but you still get moderation where you could block votes from a certain id on another server if you believe it’s being abusive in some form.

      As long as you don’t delete the voting id when the user’s account is deleted, you can avoid the votes ever being associated with the user on another server. (Since a snooping party could correlate the timing of the two deletion requests and associate the user with the votes at that time). If you did want to delete them, you could say voting id deletion happens in batches. So accounts get deleted immediately, but votes only get deleted when there’s some group size N available for deletion.

      • @chris@l.roofo.ccEnglish
        5•1 year ago

        Your idea assumes that you can just change the protocol. The ActivityPub protocol is developed under the W3C. If you just change something you are no longer compatible with other services.

        • @naonintendois@programming.devEnglish
          4•1 year ago

          I didn’t intend to imply that only one server changes something. I was intending to imply that the protocol should be updated (after review, ratification, etc.). I’m sure there’s edge cases I haven’t considered.

        • @jcg@halubilo.socialEnglish
          3•1 year ago

          This part of the protocol is not explicitly defined. In fact, section 3.1 of the AP spec says that null may be used to signify an anonymous identifier, then additionally these activities could be tagged using extensions to contain a unique identifier that isn’t the actor. The more you look at AP, the more you see how loosely it’s defined, and for good reason, it allows it to be applicable to many different scenarios (a twitter, a FB, and now a Reddit). What he’s suggesting would make it not interoperable with things like Mastodon which require an actor for a Like, but it’s not changing anything about the protocol.

          EDIT: By the way, other things don’t work when viewing Lemmy comments on Mastodon too, like downvotes don’t do anything on the Mastodon end. And you can follow Lemmy users from Mastodon but not the other way around.