You can see who upvoted and downvoted a post by viewing it in friendica.
-
That's almost as bad as using robots.txt to claim sites are private and secure and just whining that people/bots should respect it.
You should assume voter data is fully public and fully open. It otherwise is in the federated ecosystem.
The comparison doesn't work because both Lemmy and Mbin are implementing the same standard, while robots.txt is mostly an honour system.
-
It's not good practice. Really one shouldn't be assuming anything is private or some entitlement to privacy on a service where all content you post is made publicly available to any and all linked instances. They miss the point of a federated public forum. If one wants privacy, data must be kept locally only. That's why Lemmy has local-only communities, the "private" community aspect that many people want just won't be federated, because you can't make something like this private otherwise.
I know, but most people don't.
-
The comparison doesn't work because both Lemmy and Mbin are implementing the same standard, while robots.txt is mostly an honour system.
Except ActivityPub data is by in large already not private, it is handed out to any tom dick and harry who run a server and have subscribed to actors on this one, and most of the time, it doesn't even really require extra authorization. That is fundamentally how ActivityPub and federation work, but you can't have any expectation of privacy in this system when it comes to the content shared. Expecting it to be private because it's labeled is as dumb as expecting your website not to get scraped because you said so in robots.txt.
-
I know, but most people don't.
I know, it's a really big problem here and on the Fediverse in general because people get so outraged and entitled over something that just is the way things are, this wouldn't work any other way.
-
Petty mods or users would abuse this
Mods can already see voting data, at least through the API on the latest version of Lemmy.
-
but then malicious servers can lie about numbers of votes.
They already can do that by pretending to have users they don't have. It's definitely a quick way to get defederated.
And it wouldn't be caught quickly or maybe even ever if they opted to use hashes instead of just showing who voted and when.
-
The comparison doesn't work because both Lemmy and Mbin are implementing the same standard, while robots.txt is mostly an honour system.
Information not being private isn't the same thing as information being public.
I'm not sure that is a realistic expectation these days.
-
You can set a Lemmy server to proxy image requests
Exactly, that's why I said for ones that aren't cached. They can be cached, but it's not a guarantee they will be.
-
Thanks but doesn't work if you're site-banned.
You can usually use another instance that shows names if you have an account there, it'll show at least the federated stuff.
-
Except ActivityPub data is by in large already not private, it is handed out to any tom dick and harry who run a server and have subscribed to actors on this one, and most of the time, it doesn't even really require extra authorization. That is fundamentally how ActivityPub and federation work, but you can't have any expectation of privacy in this system when it comes to the content shared. Expecting it to be private because it's labeled is as dumb as expecting your website not to get scraped because you said so in robots.txt.
I didn't say it was private, I said it wasn't public, there's a difference. If you asked me what number I was thinking of I'd tell you, but that's not the same thing as the number I'm thinking of being public information. ActivityPub is, at its core, about consent. We have consented to having our data be sent to any person able to serve 200 responses on an inbox endpoint by using instances with open federation. We could, if that makes us uncomfortable, moved to a closed federation system where we only accept request from an allowlisted set of instances.
-
I get this is obviously intended behaviour on part of actpub but I'd love for there to be a pseudo-anonymous voting system too. Maybe an option to hash user credentials when added to likes to ensure that they're unique whilst obfuscating the original user.
There is already a foolproof method that is immune to any abuse of trust by admins; create an alt account.
-
Exactly, that's why I said for ones that aren't cached. They can be cached, but it's not a guarantee they will be.
Proxying is a separate option from caching. I think it was added in 0.19.5
-
Like, of course; tho any sort of "accounting" should IMO start from the base that the intent of this entire thing is to publicly share public information.
has anyone come up with possible solutions yet?
-
Upvotes seem to just federate as likes and dislikes.
That's pretty cool. Sometimes in an argument there's that (1/-1) thing going on, would be funny to see how both are downvoting each other.
-
There is already a foolproof method that is immune to any abuse of trust by admins; create an alt account.
True, but there are other benefits too. Bots can't crawl through your likes for example. Maybe you want a feature on lemmy or mastodon or whatever with anonymous polling? (ik masto has polls but for sake of argument) Maybe you're implementing anonymous polling into an app for a trade union that needs total anonymity even from admins? It's not totally unusual!
IMO it makes sense to do this at a platform level just because there's a unified implementation of obfuscation across all the fediverse for any platforms that want to use, rather than a bunch of unique solutions that would be duplicated effort.
-
I mean, seems pretty pseudoanonymous to me, unless Musk had another kid he named apj2k36 or something.
People have really weird usernames sometimes
-
Upvotes seem to just federate as likes and dislikes.
I mod a small community with like 6 monthly users, I'm the only one who post or comment and the average post have 3/4 upvotes and 1 downvote. And I always ask myself who is downvoting my submissions, because it's make no sense to me that someone take the job of pressing the downvote button on a link to a EDM set. Couldn't they just block the community?
-
Mods can already see voting data, at least through the API on the latest version of Lemmy.
How can I see this in the community I mod?
-
I mod a small community with like 6 monthly users, I'm the only one who post or comment and the average post have 3/4 upvotes and 1 downvote. And I always ask myself who is downvoting my submissions, because it's make no sense to me that someone take the job of pressing the downvote button on a link to a EDM set. Couldn't they just block the community?
Some people just downvote for the sake of it.
-
I mod a small community with like 6 monthly users, I'm the only one who post or comment and the average post have 3/4 upvotes and 1 downvote. And I always ask myself who is downvoting my submissions, because it's make no sense to me that someone take the job of pressing the downvote button on a link to a EDM set. Couldn't they just block the community?
It's not about blocking, it's about sending a message.
