this post was submitted on 04 Jul 2023
3367 points (96.1% liked)

You Should Know

33205 readers
120 users here now

YSK - for all the things that can make your life easier!

The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:

Rules (interactive)


Rule 1- All posts must begin with YSK.

All posts must begin with YSK. If you're a Mastodon user, then include YSK after @youshouldknow. This is a community to share tips and tricks that will help you improve your life.



Rule 2- Your post body text must include the reason "Why" YSK:

**In your post's text body, you must include the reason "Why" YSK: It’s helpful for readability, and informs readers about the importance of the content. **



Rule 3- Do not seek mental, medical and professional help here.

Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.



Rule 4- No self promotion or upvote-farming of any kind.

That's it.



Rule 5- No baiting or sealioning or promoting an agenda.

Posts and comments which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.



Rule 6- Regarding non-YSK posts.

Provided it is about the community itself, you may post non-YSK posts using the [META] tag on your post title.



Rule 7- You can't harass or disturb other members.

If you harass or discriminate against any individual member, you will be removed.

If you are a member, sympathizer or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people and you were provably vocal about your hate, then you will be banned on sight.

For further explanation, clarification and feedback about this rule, you may follow this link.



Rule 8- All comments should try to stay relevant to their parent content.



Rule 9- Reposts from other platforms are not allowed.

Let everyone have their own content.



Rule 10- The majority of bots aren't allowed to participate here.

Unless included in our Whitelist for Bots, your bot will not be allowed to participate in this community. To have your bot whitelisted, please contact the moderators for a short review.



Partnered Communities:

You can view our partnered communities list by following this link. To partner with our community and be included, you are free to message the moderators or comment on a pinned post.

Community Moderation

For inquiry on becoming a moderator of this community, you may comment on the pinned post of the time, or simply shoot a message to the current moderators.

Credits

Our icon(masterpiece) was made by @clen15!

founded 1 year ago
MODERATORS
 

Edit: obligatory explanation (thanks mods for squaring me away)...

What you see via the UI isn't "all that exists". Unlike Reddit, where everything is a black box, there are a lot more eyeballs who can see "under the hood". Any instance admin, proper or rogue, gets a ton of information that users won't normally see. The attached example demonstrates that while users will only see upvote/downvote tallies, admins can see who actually performed those actions.

Edit: To clarify, not just YOUR instance admin gets this info. This is ANY instance admin across the Fediverse.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 8 points 1 year ago (2 children)

Why would you want to show all information stored on the frontend?

I'm gonna start out by saying that I don't know how lemmy's federation code works. So if I host another instance and federate do I only see the upvote count or also who upvoted? Cause if the only person that can see the count is the admin of the instance the user belongs to, then there's no need to show it in the frontend. If however all you need to do to see upvote count of all lemmy users, is to host your own lemmy instance, then there should be an easy way to also access that information in the front end to indicate to the user that what they up/down vote is in fact not private.

So for me whether up/down voting is private is less of an issue as long as it's clearly communicated. Again if only the instance admin the user is part of can see the count, then that's essentially "private" as you are trusting that entity already ^^

[–] [email protected] 3 points 1 year ago (1 children)

If however all you need to do to see upvote count of all lemmy users, is to host your own lemmy instance, then there should be an easy way to also access that information

I haven't thought of that, and you may be right on this.

However, I don't fully understand this part:

there should be an easy way to also access that information in the front end to indicate to the user that what they up/down vote is in fact not private.

But it's true that my brain today doesn't really want to work. You mean by some kind of API call can reveal these information?

[–] [email protected] 4 points 1 year ago

However, I don’t fully understand this part:

there should be an easy way to also access that information in the front end to indicate to the user that what they up/down vote is in fact not private.

But it’s true that my brain today doesn’t really want to work. You mean by some kind of API call can reveal these information?

Basically what I meant is some way for the user to see who up/down voted what. Maybe hovering the up/down vote button shows a field you can click on that say votes or something and that then redirects you to a different page that shows who upvoted and downvoted that specific post/comment. The exact details don't really matter. My point was basically that if something is accessible but only via hidden means that are not obvious to the end-user, they may wrongly assume that information is private. So by making it easily accessible to end-user, you also clearly indicate that that information is publicly accessible ^^

[–] [email protected] 2 points 1 year ago

Again if only the instance admin the user is part of can see the count, then that’s essentially “private” as you are trusting that entity already

Until you get rouge instances or rogue admins on seemingly reliable instances willing to fuck with vote numbers for money. A full open system does help with accountability and the ability to discover corruption/deception by admins. I'd rather have the openness than allow instances to create their own fiefdoms with no externalized accountability in an open federated system like this.

The scummier versions of old reddit power mods are probably salivating at having their own instance farms to sell upvote services to advertisers and nefarious groups to with the concept of hiding vote details from downstream instances, so it is easier to obfuscate their activities and more difficult for external analysis to discover and expose.

Keep it all open and just advocate and educate the end users to create anonymized user accounts with unique emails if they want their personal privacy.