Allow it to be configurable by server or community. Some communities may benefit from allowing the public or mods to see votes, while others would be hurt by it.

[–] FiskFisk33@startrek.website 4 points 2 months ago (1 children)

mods already see votes

[–] PeriodicallyPedantic@lemmy.ca 5 points 2 months ago (1 children)

And that should probably be configurable

[–] FiskFisk33@startrek.website 3 points 2 months ago (1 children)

To truly make that change, they would have to change how the federation works. Right now its visible to anyone who runs a server your server federates with.

I hear Mbin users can already see it.

[–] PeriodicallyPedantic@lemmy.ca 2 points 2 months ago (1 children)

Yeah, and I think that's the argument about making it public.

But access rights to stuff seems like the kind of thing that should be configurable, even if it requires a change and isn't backwards compatible

[–] FiskFisk33@startrek.website 4 points 2 months ago (1 children)

There I agree with you.
Making it public right now is useful to remove a dangerous false sense of privacy. But in the bigger picture I agree with you.

I wonder how one would solve that though. If you send a "vote" request without any user data, what stops you from sending 100?

[–] PeriodicallyPedantic@lemmy.ca 1 points 2 months ago* (last edited 2 months ago)

The data needs to be sent from the voter to the server that owns the post. But the server that owns the post can anonymize the data before it sends it to clients or other servers.

That said I don't have deep understanding of activitypub. Its possible that something would prevent this, like if votes made their way to the server that owns the post by way of telephone game rather than directly from the client or the user's home server. But that seems like an unreasonable design, so I doubt (hope not) that is the case.