Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 162 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

Seeing a post voted +10 doesn't tell the full story. The votes could be split:

  • +10/-0, signaling a good post
  • +35/-25, signaling an awful post

Lots of downvotes on a positive-scoring post might indicate a wrong answer, a poor but popular question, or a controversial meta opinion. A reader should be warned of these even if they don't compulsively click vote counts to check the split or lack the 1000-rep privilege to do so.

So, I propose showing the number of upvotes and downvotes to all users, including those not logged in, by default without needing a click.

Votes up don't cancel votes down, both in meaning and in rep. They only cancel in that the votes sort order treats them that way, though alternatives have been suggested. The net score is a poor statistic to show because it conflates two attributes:

  • Quality, as suggested by the relative ratio of upvotes and downvotes
  • Visibility, as suggested by the total number of votes

These can be quite different, as witnessed by the Fastest Gun in the West problem and Hot Network Question voting trends.

There have been many discussions about removing or lowering the privilege to view vote counts on click (1, 2, 3, 4, 5). I question though why the counts are hidden behind a click in the first place. Answer from many years ago mention a performance cost (1, 2) – is this really still a limitation?

share|improve this question
    
If you want this, then there's the Auto-Load Vote Counts userscript at Stack Apps, but you need to have the rep, and it only works for you and not everyone else... :/ – ᔕᖺᘎᕊ 5 hours ago

I think performance is still a major concern. As you might have read from those other posts, the post score is kept as value in the posts table. That value is pre-calculated based on the upvotes and downvotes. That means that it doesn't need additional fetches to get the post score from the votes table.

You could say of course that the team could add two more aggregated columns in the posts table, one for upvotes and one for downvotes, which are calculated the same way the current score is. I am not sure what the impact would be in ways of performance or development time, but it seems the only feasible way to improve performance that much that it can be shown to everyone.

On the other side, I don't mind that new members don't see it. We don't want to confuse them too much with the way SE works, they are puzzled enough already. Step by step they are made familiar how things work. Showing too much information might not be a good idea for that reason.

share|improve this answer

I don't agree +35/-25 is an awful post and the reputation algorithm does not either.

You have to have the rep to see up and down. It is a cleaner UX withOUT the split (IMHO).

share|improve this answer

I mostly disagree with your premise. There obviously is a difference between a question scoring +10/-0 and a question scoring +35/-25 but not enough of a difference to be adding more features and UI for new users. It's certainly useful and interesting, but it isn't essential.

Post score is a good quick and easy measure of a posts quality, but it doesn't, and shouldn't, tell you everything. A post should stand on its own merit and you don't need to see how many specific votes a post has to determine its usefulness (the only exception is possibly meta posts where a consensus through votes is important—but that's not what this request is about). A single score is also much easier to process than having to compare the ratios of two scores across different posts.

Arguments that post score alone isn't enough to tell you the usefulness of a post are expecting too much from the score—vote counts certainly tell you more, but they're in no significant way more reliable.

The ability to see vote scores is also the main part of the Established User Privilege which is the first "milestone privilege". The whole reputation system is built around unlocking features at set targets (whether that is a good system or not is besides the point of this question) and as a target, unlocking vote counts is useful enough to be a "milestone" feature but not essential enough to be needed before that. If vote counts were always visible there'd probably need to be something to replace it as the first "milestone privilege".

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .