The mod banning these users is the same mod who made the posts they downvoted. This is mod abuse, turning the downvote button into an auto-self-ban button.

The message is “If you disagree with me, you will be banned”

Monitoring and banning users for using lemmy as intended to signal boost your opinion should be grounds to have all mod privileges removed. This behaviour undermines the integrity of the server and the wider fediverse.

  • remon@ani.social
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    2
    ·
    24 hours ago

    There’s not really a way to do votes privately on a federated system.

    It’s a minor technical problem.

    • Mose13@lemmy.world
      link
      fedilink
      arrow-up
      6
      ·
      edit-2
      23 hours ago

      How should it work in your opinion? Like technically, how would you federate but also vote privately?

      • remon@ani.social
        link
        fedilink
        English
        arrow-up
        8
        arrow-down
        1
        ·
        edit-2
        22 hours ago

        You use a one-way hash instead of the current identifiable key that is used to store the vote value.

          • remon@ani.social
            link
            fedilink
            English
            arrow-up
            3
            arrow-down
            2
            ·
            edit-2
            22 hours ago

            I don’t see how replacing a unique id with a unique hash would have any effect on that. Even if you use a variable hash (that would change every time you change your vote) you just have to make sure that the backend properly removes the old value on a new call.

            • jet@hackertalks.com
              link
              fedilink
              English
              arrow-up
              8
              ·
              edit-2
              22 hours ago

              My point is that if a U user is on L local instances and R remote instance gets the vote, how does R know if U is double spending or not?

              • remon@ani.social
                link
                fedilink
                English
                arrow-up
                3
                ·
                21 hours ago

                I see, guess I underestimated the problem a bit, I have to think about it some more.

              • Aceticon@lemmy.dbzer0.com
                link
                fedilink
                English
                arrow-up
                2
                arrow-down
                1
                ·
                edit-2
                18 hours ago

                Hash the whole fucking thing and store it with the entity being voted on.

                UserID, UserServerID, EntityID, EntityServerID all together hashed.

                Mind you, I’m assuming those pieces of information exist because thingID + thingServerID makes sense as a way to identify “thing” (user, comment, post) in a federated system.

                Server is the server that hosts “thing”: the server where the user is registered, or the server hosting the forum where a post was made or a comment was made under a post.

                On an incoming vote, server calculates the hash. If the same hash is already present, server doesn’t accept another vote if it’s the same way or changes the existing vote if the new one is different.

                Mind you, this is all blue sky thinking based on how I myself would design such a system as I can’t be arsed to go learn Lemmy’s API and data model just for this.

                • jet@hackertalks.com
                  link
                  fedilink
                  English
                  arrow-up
                  6
                  ·
                  18 hours ago

                  In your model Remote server would still know about User’s votes, which is what we have now with lemmy.

                  • Aceticon@lemmy.dbzer0.com
                    link
                    fedilink
                    English
                    arrow-up
                    2
                    ·
                    17 hours ago

                    So in the data-model the votes are linked to the User rather than to the entity being voted on?

                    I supposed it makes sense considering that the user him/herself does get displayed in a prominent way where they voted and how.

                    I hadn’t considered that side of the data flows :/