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 Should we start displaying the score of a post instead of the raw votes?

Parent

Should we start displaying the score of a post instead of the raw votes?

+10
−2

Currently, when viewing a post, Codidact will show you the raw votes on a post, with the breakdown into upvotes and downvotes:

Screenshot of the voting buttons, showing +12 and -1.

There's been some feedback that this is a bit too much to show, especially coming from platforms like Stack Exchange where they generally just show the aggregate score of upvotes and downvotes as one number (with the option to expand the votes to see the split). We decided to show both counts automatically to better show when there's controversy.

However, we now also have another option. We have a method for scoring posts that assigns a score between 0 and 1 to each post.

Perhaps instead of showing the raw votes on each post, we should instead show the post score (e.g. 0.81363... or 0.3793...), rounded to the nearest two or three decimal places (so that it would show as 0.937 or 0.276), with the raw votes available on request, perhaps either on click or in the tools menu.

This would take people a bit of time to get used to, but it might be worth that initial adjustment time, since this... is our scoring system and we want people to be familiar with it quickly.

This has the added benefit of making it much clearer why answers are sorted the way they are by displaying their score (that's currently computed without being displayed) for everyone to see. The raw votes matter less than the computed score.

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

1 comment thread

Two degrees of freedom (2 comments)
Post
+8
−2

I agree that on a list of questions, one clear indicator of fitness is most helpful. On a post's own page, it might make more sense to also show the up- and down-vote counts.

Given that the "score," here, does not directly represent anything anyone can count, but rather is the result of plugging the up- and down-votes into a not-fully-intuitive continuous function, I think that showing the literal number that comes out of that function would be more confusing than helpful. Instead, I suggest representing it with a Likert scale, with a Help topic that provides both the formula and broad qualitative interpretations of the various scores. For example:

  • ↓↓ (Wilson score 0 - 20%): The community has expressed a clear consensus that this is not a helpful post.

  • (Wilson score 20% - 40%): There is some indication from the community that this is not a helpful post.

  • (Wilson score 40% - 60%): The community hasn't expressed a clear consensus regarding how helpful this post is.

  • (Wilson score 60% - 80%): There is some indication from the community that this is a helpful post.

  • ↑↑ (Wilson score 80 - 100%): The community has expressed a clear consensus that this is a helpful post.

In place of the ASCII arrow glyphs in this example, some variation of a traditional five-level signal-strength symbol could be used, such as:

Five-level signal-strength symbol
OpenClipart, Public Domain

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

General comments (2 comments)
General comments
DonielF‭ wrote over 4 years ago

Or maybe just a color coding: red for 0-20%, orange for 20-40%, grey for 40-60%, blue for 60-80%, and green for 80-100%. You got a chuckle for the Wi-Fi symbol, but I think that'd be more confusing than anything. I give you a two-headed grey arrow for your other suggestion.

Karl Knechtel‭ wrote 12 months ago

I was inspired by this idea, but I think it loses too much information as described. I don't think it's too much to show an analog quantity such as Wilson score in an analog way, as long as it's presented graphically rather than numerically. For example, with a shape whose size and/or colour varies smoothly. I also think the total vote information is important, and it's a big part of why we show up/down tallies instead of a (rounded) Wilson score up front: because it indicates how much attention has been paid to the post, not just a quality consensus.

I just now added an answer with my own proposal to try to incorporate all that information.