You can see who upvoted and downvoted a post by viewing it in friendica.
-
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.
-
How can I see this in the community I mod?
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.
-
Proxying is a separate option from caching. I think it was added in 0.19.5
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 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 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".
-
The comparison doesn't work because both Lemmy and Mbin are implementing the same standard, while robots.txt is mostly an honour system.
idk, the label is also an honor system, if it can be just ignored like robots.txt.
-
This is nothing new. Fire up any ActivityPub server and you can see everything over the wire. As a Lemmy admin of my server of just me, I can also see it in the UI.
Wouldn't you be able to see it by
curling the outboxes? -
idk, the label is also an honor system, if it can be just ignored like robots.txt.
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.
-
System shared this topic on
