I read on reddit that on Lemmy you can see users’ upvote/downvote history. I therefore expected to be able to see upvote/downvote breakdown by user for my own comments. But couldn’t find this. Does this feature exist or is that a myth?

  • r00ty@kbin.life
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    Also without identifying the user it becomes hard to know what’s a unique like and what is a duplicate. I suppose a workaround would be for the user’s instance to keep a record of who liked what, and then just issue just the unique like IDs (which can be traced back to the user only on their home instance).

    It would need to be a bit smart. Say the same user toggles their upvote on and off. The upvote for a given topic I think would need to be a hash of the topic/comment ID + user ID so that the same ID would be re-issued to prevent the upvotes/cancels falling out of sync.

    It’s a lot of effort really for keeping something such as a like private.

    • cwagner@lemmy.cwagner.me
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      That wouldn’t bring any benefit over only federating totals, or am I missing something? As soon as you federate anything that allows discounting blocked users, no matter what algorithm you use (besides maybe zero knowledge proofs, I guess, which are black magic to me) , the votes will be essentially public

    • HamSwagwich@showeq.com
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      What if the post is edited at a later time? Then all those votes become invalid. It’s not practical with the way ActivityPub is designed. Honestly, it’s designed the way it is for a reason… if you aren’t willing to own your participation on a public forum, you shouldn’t be on a public forum.

      • r00ty@kbin.life
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Why would editing do that? I was talking about using the ids which wouldn’t change on an edit.

        In any case, I don’t have a problem with this info being federated. Some people do, so it’s worth talking about ways it could be done.

          • r00ty@kbin.life
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            I was suggesting (I actually clearly said it in both comments) hashing the post/comment ID + userid NOT the content. Just enough info to get a unique ID. We don’t need it not to be non-reversible. Just a unique ID for the like.