![User's banner](/_next/image?url=https%3A%2F%2Fmedia.gehirneimer.de%2Ff1%2F58%2Ff158fbfa26d6cf8cb6761f426d71d980eb47a8fdec3afa4c907247211b8a36a1.jpg&w=2048&q=75)
![Avatar](/_next/image?url=https%3A%2F%2Fmedia.gehirneimer.de%2F31%2Ff0%2F31f0394dafa8dcf6f84b7c732065eb931f44e0907042eaf1b71f4b5f7f125b26.jpg&w=3840&q=75)
![Avatar](/_next/image?url=%2Flemmy-icon-96x96.webp&w=3840&q=75)
BentiGorlich
Beruflich Web-Entwickler, privat ein Ober Nerd und Links-Grün versifft…
Musik Liebhaber, von #kpop bis #metal alles dabei
Ansonsten bin ich auch gerne mit der Kamera unterwegs.
Entwickler und Maintainer für #mbin
ich bin auch auf mastodon: @BentiGorlich
Ich betreibe thebrainbin.org, gehirneimer.de und wehavecookies.social
I did my part 😇
We can look at PeerTube for an example of a system that could be shaped into what I meant:
when you look at a post (video) from peertube it links lists for likes, dislikes and shares (so basically upvotes, downvotes and boosts). These collections contain a totalItems
property, but also list the peoples identities, but just imagine that it wouldn’t be there.
When a user now likes the video, the creator of the video now sends out an Update
acitivity to all subscribers. Now all subscribers can update the counts for likes, dislikes and shares. Only the “home instance” of the creator account knows about all votes, nobody else does, but nevertheless everybody else can now how many likes, dislikes and shares there are.
If we compare that to mastodon the first part of the statement is still true:
Only the “home instance” of the creator account knows about all votes, nobody else does
But that means that most instances just show 0 likes for most of the posts, because your instance only knows about likes originating from your instance…
As for your proposition: I couldn’t follow for some of it. However I think the risk of an actor abusing the creation of fake accounts and fake upvoters is not really a risk, that is what defederation is for… I would argue very much agains a lemmy specific protocol and some judge instances simply because then big instances would just have pretty much all the data again and it would definitely hurt interoperability because lemmy devs can then just take the easier route instead of implementing something according to AP spec
You cannot make votes completely private, one instance has to have the authority over which votes do exist. This instance should be the origin of a post or comment.
At the moment it works like this: you upvote a post, this upvote gets send to the author of said post AND the magazine and that magazine then broadcasts your upvote to all subscribers of said magazine.
I could imagine that the process looks a lot different: you upvote a post, this upvote gets send to the author of said post, the author of the post then sends an update to the magazine saying how many people have now upvoted their post and the magazine then broadcasts this info to every subscriber of the magazine.
With that you would of course have new limitations concerning moderation and maybe there are trust issues regarding the correct reporting of that upvote count, but only the author of the post (and their instance ofc) could technically know who upvoted their post. As in everything here this is a compromise and whether the gained privacy is worth the other limitations, I don’t know
Upvotes were already implemented when we did the fork. I guess we just never really thought about it. I honestly just have no opinion on whether upvotes should be public or not, so I don’t mind them being public, but I basically never check who upvoted my posts anyway, so might as well be removed… If people care about this I’d say it is just up for discussion…
I think that’s is called a “temporary” solution 😁