Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Comments on General discussion on making votes public

Parent

General discussion on making votes public

+7
−1

Make vote secrecy a per-community choice, because some communities might prefer voting transparency over voting privacy.

Side-question. Why voting is secret in other Q&A platforms?


Origins in the Community Server (direct link to conversation), raw transcript follows (but expect format inconsistencies):

Transcript

Mithical
Votes are anonymous. Scrounging vote stats on profile pages to see who's cast votes on a small site to try to figure out who's downvoted something is highly discouraged, and calling people out for it is definitely over the line.

DonielF
Why are vote stats displayed on profiles?

Mithical
uploads a pic of Shrek captioned "good question"

gs
let's read the git log about it
I traced it back to the earliest user profile pages written back 5 years ago
I couldn't identify a reason, I'd guess "just because it was easily and readily available" the first living version already had that https://github.com/codidact/qpixel/commit/90a8cb1683cc90ad8bd928742c3a32d5ee761d64

cellio
When Art wrote QPixel originally he was probably thinking more along the lines of an SE clone as opposed to a new thing. Originally Codidact was going to start fresh with all new code, building from the start what we wanted to have, but that turned out to have issues. So we decided to start with QPixel and evolve it into what we want. This is one of those underlying assumptions, inherited from SE, that I'm guessing no one thought about. I think it makes sense to show voting history only to the user, not publicly.

gs
what if we went all the way around. Instead of making everything vote-secret, make everything vote-public
excuse me I ignore if there's already a meta post about it

DonielF

what if we went all the way around. Instead of making everything vote-secret, make everything vote-public

@gs NONONONONONONO

gs
why not? I mean

DonielF
Already with reactions and “me too”‘s we’ve had people say they’re only interested in voting and the like only because of anonymity involved; they don’t want it to be personal.

gs
if voting is even moar secret than in SE, there'll always be people thinking staff cheats scores

DonielF
As if scores do anything?
Also, everything is open source
There’s no way for staff to cheat votes

ShowMeBillyJo
Well, direct database manipulation - the data isn't open source

gs

Already with reactions and “me too”‘s we’ve had people say they’re only interested in voting and the like only because of anonymity involved; they don’t want it to be personal.

aha so r you basically saying it's a community choice?
and I mean a per community choice

ShowMeBillyJo
I think it'd be an interesting thought exercise to explore fully open votes, even if it doesn't get implemented

DonielF

aha so r you basically saying it’s a community choice?

@gs I’m not necessarily saying that, but I’d be comfortable with such a policy.
Look, if y’all really think this is something that should be explored, Meta awaits

gs
I'm lazy to write the post but give me a link I can upvote

Mithical
There are also some ancient forum discussions about this.

[...]

Mithical

There are also some ancient forum discussions about this

https://forum.codidact.org/t/proposal-votes-scores-and-answer-order/385/19

Relevant forum discussion: https://forum.codidact.org/t/proposal-votes-scores-and-answer-order/385/19

History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

General comments (11 comments)
Post
+1
−3

Countering some Moshi's claims.

False accusations of revenge voting. (whether knowingly or not) That is, stuff like "I know @downvoter doesn't like me, that must be why they downvoted." and "I downvoted @downvoter's post a few days ago, they must be downvoting me because of that"

When downvotes are public, make required posting a reason for downvote. Then once you have the feature, allow commented downvotes on sites where downvotes are private.

Actual revenge voting. I really fail to see how letting people know who downvoted them is supposed to discourage downvoting in revenge. At least with private votes, they won't know who to target.

Knowing who hates others is a good first step towards their reconciliation.

Discourages downvoting. Most people already don't like giving negative feedback; signing downvotes will only make it harder.

You justify a site design choice on the timidity needs of a minority group. Instead, let that minority downvote privately, but why force their needs on other people?

It still doesn't do anything about downvoting without explanation. The main issue with downvotes is that they aren't very constructive. They say "this post isn't good" without explaining why the post isn't good. Showing who downvoted doesn't do anything about this issue, and in fact people might rely on their name instead of an explanation a la "Let my reputation tell people this post is bad instead of explaining why it's bad."

I see it as a way to facilitate communication...

"Heaviness" of certain users' votes. Expanding on the previous point, if the well-known user A downvotes a post, then the community might be biased to downvote because "A thinks it's bad so it probably is."1 The same goes with upvotes; users might be biased to upvote if user A upvotes.

Sites metas can easily fight this by insisting on not falling in authority fallacy.

History
Why does this post require moderator attention?
You might want to add some details to your flag.

1 comment thread

General comments (4 comments)
General comments
Moshi‭ wrote over 3 years ago

"Instead, let that minority downvote privately, but why force their needs on other people?" I was under the impression that we were discussing the all or nothing choice. If that wasn't the case, then I'm find with the compromise of letting people chose to sign their votes.

Moshi‭ wrote over 3 years ago

"Knowing who hates others is a good first step towards their reconciliation." I don't really see your point with that. Downvotes are not equal to hating the poster; this attitude is exactly why I argued against signing votes since it would cause needless drama.

Moshi‭ wrote over 3 years ago

"Sites metas can easily fight this by insisting on not falling in authority fallacy." Insisting in what way exactly? The help page (that no one reads)? A meta post (that'll get buried)?

Derek Elkins‭ wrote over 3 years ago

This answer seems to be heavily premised on the idea that "reconciliation" is a net win for the participants. This would probably be true if reconciliation didn't take time and effort, but it does. Speaking for myself, even if reconciliation with someone accusing me of revenge voting was guaranteed to produce an outcome favorable to me, it wouldn't be worth the effort. A few hours of frustratingly defending myself is not worth having some rando slightly less miffed at me.