New feature: Vote Neutralization
You've just voted on a Gulch post and, "DAMN IT!" you hit the wrong button and voted the wrong way.
Easily solved: click the opposite button and your vote is switched. Nice.
But, what if you just wanted to back out your vote? What if you hit a vote button accidentally when you didn't even mean to vote? Until now, you've been out of luck.
Introducing "Vote Neutralization."
From here on out, if you ever mistakenly vote and simply want to back it out, just click the same button again and, voila. Go ahead and try it out on this post, or any post, to see it work.
And then vote this post up permanently because you love it.
Easily solved: click the opposite button and your vote is switched. Nice.
But, what if you just wanted to back out your vote? What if you hit a vote button accidentally when you didn't even mean to vote? Until now, you've been out of luck.
Introducing "Vote Neutralization."
From here on out, if you ever mistakenly vote and simply want to back it out, just click the same button again and, voila. Go ahead and try it out on this post, or any post, to see it work.
And then vote this post up permanently because you love it.
Previous comments... You are currently on page 2.
You're seeing -2 and +2 because you're voting in the opposite direction of a previous vote. If you downvote something you've previously upvoted, it will lose 2 points because you're not neutralizing, you're actually changing your vote.
Let's see if I can illustrate it...
1. A new post is created by someone else. It now has a +1 score.
2. You upvote it. It now has a +2 score. Remember, you have cast a vote FOR the post.
3. You change your mind and downvote. It now has a score of 0 because you cast a vote AGAINST the post.
1 + 1 = 2
1 - 1 = 0
This is why it LOOKS like it's losing 2 points. It's not really though. It's simply tallying your vote correctly. This is why we had to add the neutralize function - so when you change your mind, and back out a vote, it loses only 1 point.
Make sense?
I am accessing the page using Firefox 22.0 -> Ubuntu 12.04 LTS -> Intel
I did not do a force refresh before either vote.
Just kiddin'. It'll be fixed in a second. Stand by.