Hello all!

As of yesterday, I have updated the the instance to 0.19.2-rc.5. This should fix some of the remaining federation problem.

This morning it was brought to my attention through the Matrix chat that a feature has been added to the UI to allow admins to view votes: https://github.com/LemmyNet/lemmy-ui/pull/2303

I would like to add a bit of context. Viewing votes has always been possible in at least two ways:

  • Since votes are stored in the database, admins with access to the database have always been able to retrieve the list of voters by running a postgres database query.

  • Some applications in the fediverse will display votes by default. For example, content federated with friendica displays the votes as “likes/dislikes”, so any user can see federated votes.

What this feature has changed is that admins, regardless of whether they have access to the server, are able to see the list of up-votes/down-votes through the user interface.

This is effectively making a “hidden” admin feature more transparent. This can also help admins easily identify if bots are being used to mass down-vote.

I am bringing this up explicitly here because I think users might be interested in knowing if their votes can be seen, and so I want to be transparent about this change and about votes in general.

I also have some thoughts that I would like to discuss. If users are uncomfortable with admins having this power, I could remove this feature from this instance. But that would only be symbolic, as the votes can always be retrieved from the database anyway - and other instance admins will still have this feature to see federated votes.

I can also keep it this way. Only admins can see votes, and I can simply not abuse that power.

I can enable this feature for every user. Then everyone can see everyone’s votes.

Another option is to disable down-votes altogether.

If anyone has any thoughts/opinions about this, please let me know. I’m curious and interested in finding a good way to handle this.

  • Mothra@mander.xyz
    link
    fedilink
    arrow-up
    3
    ·
    10 months ago

    I’m not sure I’m 100% following with what’s possible in terms of enabling users’ access to see who voted what.

    If it’s possible to make the feature available I’d support that, but honestly I’m not phased if it’s only admins and tech savy outsiders who can access this info. I wouldn’t want you going out of your way to implement something like this, how much time and energy you want to spend on it is up to you!

    But above all I appreciate that you are being transparent about it and taking our opinions into account.

    • Salamander@mander.xyzOPM
      link
      fedilink
      arrow-up
      2
      ·
      10 months ago

      I like the suggestion of [email protected] of simply making a bigger effort of letting users know that votes are “semi-public” information in the fediverse, and I have opened an issue to suggest implementing that approach (https://github.com/LemmyNet/lemmy-ui/issues/2316)

      But above all I appreciate that you are being transparent about it and taking our opinions into account.

      One of the big selling points of Lemmy is privacy, and so many users do have a high expectation of privacy. It is important to be very clear and transparent about aspects that can raise privacy-related flags. Votes need to be public for the federation to work and to prevent double-counting, at least the way they are currently implemented, so transparency is the best solution.

      The argument for letting everyone see the votes is a bit more tricky. On the one hand, if the tech-savvy can do it, then why not just let everyone do it? On the other hand, if it is easy to do, you make it easier for users to witch hunt and attack each other on the basis of how they vote.

      Putting some additional thought on it… Enabling it for everyone has other privacy implications. For example, old votes would also become public and I can’t get backwards-consent from everyone. Votes from selective instances federating with us will too. I would need to wipe all of the votes from the instance before enabling that. I think making the effort to be transparent is a better approach.