Recently my account gained the privilege to review questions on Stack Overflow. While doing this, I came across a low quality answer. Following the review instructions, I downvoted the answer and left a comment explaining how it could be improved.

Trying out the review queue for the first time

Neat. This post reviewing thing doesn't seem so hard. Now I'll just click "I'm Done" to move on to the next post, and...

"You need at least 500 reputation to review first posts"


Turns out my account had just reached the required 500 rep for the review queue, meaning a single downvote was enough to put me below the rep requirement.

I'm sure this won't be an issue for long. After answering a few questions, I should (hopefully) have enough rep for this not to matter. But this scenario can be confusing for a user learning how to properly use their newly accessible review queue.

Can some type of warning or indicator be added if downvoting a post would put your account below the reputation requirement to access review queues?

  • 1
    Its probably true of any privilege that lets you trade reputation for anything. – Journeyman Geek Apr 23 '17 at 0:42
  • 3
    Declining this because the complexity that avoiding it would add exceeds the potential benefit. Also, Gnemlock's excellent answer. – Shog9 Jan 11 at 1:33

I believe we already have this measure in place, via the help center:

You lose reputation when:

We can not expect new users to read the help center, but they should; the main articles, at least. We can all admit that we would have a lot less cleanup regarding new posts if they did. The above mentioned is one of these main articles.

At the end of the day, I feel that an additional warning in the review queue has some good merit to it; but I see other problems with this feature, more specifically, the extent of the effect it will actually have.

  • If we put up an additional warning, who are we actually targeting? First time reviewers who are literally on the borderline for having that privilege. I will leave this to someone else to gather analytics regarding how frequently this actually happens; I feel safe speculating that it does not happen very much, at all.
  • Any additional warnings will not bear any effect if the user does not actually read the warning; we have to take that into consideration. We can not assume one way or the other, but we already know that in the few cases where such a warning would assist the user, they have already chosen against reading about our basic practices in the help center.
  • I know that some of our sister sites move a lot quicker than others, in regards to reputation gains. However, in my experience, by the time you reach the minimum reputation requirement to partake in reviewing you should already have enough practice to understand that when you click the down-vote, you lose a point of reputation.
  • As you have already pointed out, the few times where this user case would lead to user frustration, it is literally the matter of a single reputation point. Assuming the user continues to conduct themselves appropriately, they should be able to reclaim that reputation point fairly quickly.
  • Implementation could be tricky; A clear warning on the screen, itself, pushes towards interface overload. It's like having all of the buttons visible at any given time; it looks bad, and it lessens the user experience. The only other implementation I could think of would be a pop-up, but then we have the additional question of will users pay attention long enough to notice the pop-up, and if they do, will they go back and check it or gloss over it immediately? I feel it is uncommon to expect users to hover their mouse over the downvote button for an extended period, for example. If I choose to vote on a question or answer, my mouse hovers over the button for such a split second that it took me a very long time to even notice the current pop-ups that display.

As such, I vote against this proposition. Not because it is a bad idea, but because it is not feasible in comparison to how it would affect typical users, the workload, and the effect on the actual interface.

| improve this answer | |
  • 1
    Fair assessment. It's not a critically important issue by any means. I mostly posted just so this small quirk could be documented. – Stevoisiak Apr 23 '17 at 1:02
  • 1
    @StevenVascellaro, for further consideration, I can think of one way to implement it. When you vote, your vote is locked after several minutes. If you attempt to renege, a popup appears in red, stating "you can not until the post is edited etc. etc.". This certainly stands out; perhaps in the minor situations this sort of popup could come up instead of applying the downvote, informing the user that this downvote would result in them being disqualified from the review queue, and asking them to click the button again to confirm their vote. – Gnemlock Apr 23 '17 at 1:09
  • 2
    I will refrain from posting that suggestion, because I do not think we should affect users voting patterns in this way, but feel free to flesh that idea out more if you wish to post your own answer, later. – Gnemlock Apr 23 '17 at 1:11
  • 4
    Would like to point out that it's possible to give away all your reputation with a bounty if you only have say 151 reputation, and there isn't a warning against doing that, so how is doing a review at the percise reputation required to do reviews any different? Besides a downvote didn't have to issued, and if the contribution is that bad, when it's deleted your reputation will be returned. – Ramhound Apr 23 '17 at 2:55

You must log in to answer this question.

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