You can see who upvoted and downvoted a post by viewing it in friendica.
-
Yeah, let's make things less abstract and talk about real examples.
piefed.social is not sending the real voters out. You think that alone should be grounds to get lemmy.ml (your instance) to defederate them. Am I understanding you correctly?
-
Oh no, I think defederation is only necessary when an instance becomes a problem. Until piefed.social becomes a haven for trolls to manipulate vote counts (which might never happen) then it's fine.
But if a dozen anonymized piefed.social votes start downvoting everything I say because they're monitoring my account then their admins would need to do something about it. If they didn't, I'd want defederation.
-
I've gone to my community and to specific posts, but can't work out how to show downvotes. Can you shed a little light on how to see them please?
-
Who cares? If your upvote or downvote or any other activity you deliberately perform on a public platform is something you're embarrassed about and wouldn't be willing to do in a face to face engagement you probably shouldn't be doing it.
-
I agree, and if you absolutely must, then maybe make an alt?
The main problem is most people assume their votes are private, as they are private on reddit.
-
You can use the Tesseract Lemmy frontend to view votes in your communities. However it will only work on instances on version 0.19.8 or greater, so if your mod accounts are on an instance like that it won't give you the option or let you see them.
-
Oh I didn't know that, that's good. Though I think the point still stands since it's not a guarantee instance admins will use it (unless it's a default).
-
I think you're misunderstanding just like the Mastodon users who think every tool should be opt-in. The consent piece IS moving to a closed system with whitelisted federation. If you're giving data out publicly with no restrictions but trying to put stipulations on how it's used, it's the same as trying to enforce control through robots.txt, which is by the way a standard protocol.
So if you're going to whine about votes being shown, you should be using a whitelist to block those actors from seeing it, and should be using authorized fetch to limit access to those whitelisted instances specifically, otherwise this is every stupid argument about "why robots.txt should be respected".
-
idk, the label is also an honor system, if it can be just ignored like robots.txt.
-
Wouldn't you be able to see it by
curling the outboxes? -
I didn't explain what I meant very well. To scrape a website you don't need to understand robots.txt, implementing robots.txt is something you do to be a good netizen. But to get like info from Lemmy, implementing ActivityPub is a requirement.
Now I'll admit, it's not a great system and I do wish we had something better, but I also don't think "this isn't a good way to communicate preferences" is a good reason to ignore them.
