6

Currently, we can't un-upvote or un-downvote answers we voted on in the past. This is to prevent strategic voting and is generally a good thing©.

However, sometimes I want to un-upvote or un-downvote an answer once I changed my views on the subject or know it better. Gaining an understanding in a language/framework/library/system is very common when programming and often in retrospect I'd vote differently.

It would be really nice if we could retract votes after a duration - probably a month.

Related questions on meta:


Opening on Meta SO and not Meta SE because I'm not sure this "learning of the field" applies in some sites - maybe it does.

3
  • At that point you've defeated the purpose of locking votes in the first place, as someone can strategically vote and then go back a month or however long you set it later to undo the downvotes.
    – Servy
    Commented Jun 12, 2015 at 15:57
  • 1
    @Servy you really think people would go back a month and do that? The fact every company out there has a "money back guarantee" people miss indicates otherwise. Commented Jun 12, 2015 at 15:59
  • 4
    Well the feature is there because people were coming back several days later to undo the votes. If you're assuming people are never going to come back to undo the votes then you might as well just get rid of it entirely. Someone who's going to go back in a few days is just as likely to come back in a month.
    – Servy
    Commented Jun 12, 2015 at 16:01

3 Answers 3

8

I usually just suck it up.

Sometimes I'll post a new answer if I later realized a better answer exists.

Sometimes, when e.g. I find I was wrong to downvote (e.g. after other people clarified context I missed) I'll explicitly edit the post with a comment like

<!-- edit so I can un-downvote -->

That unlocks the vote too. It's almost cheating the rules, but can be done ethically by leaving the comment for the OP. (Sometimes I'll leave a readily visible comment for other users too, or just +1 an existing comment that already makes the required point).

Very rarely I would take the time to remove an upvote. I'm not sure I ever did.

6

At the rate that programming languages change or advance, some answers quickly become deprecated or wrong. Removing this vote lock would give people a chance to remove votes on say, a mysql_query PHP question, that was relevant when mysqli_* or PDO was not around.

I'll inform Woodhouse to place my upvote when he gets back with my Tactilnecks.

3
  • 3
    Very solid use case. Commented Jun 12, 2015 at 15:59
  • Answers don't generally become "wrong", even if applied to an older context. In addition, I don't think "outdated" answers deserve downvotes (in that what appears outdated only needs to be put in the context of the version at the time it was answered). I'd agree that some mysql_query answers have the problem of being vulnerable to injections for example (even with "real escape"), but they had the problem back then, as well as now (which could warrant downvotes back then too).
    – Bruno
    Commented Jun 12, 2015 at 16:03
  • Just for clarity, notice I said remove vote, not downvote Commented Jun 12, 2015 at 16:06
2

I've never really been all that enthusiastic about the strategic voting argument here. While I suspect there is probably some subtle influence, I'm skeptical that it warrants such a heavy-handed restriction.

But there are other behaviors that do warrant it.

None of these are hypothetical, BTW. Nor is this list exhaustive. Folks have done or tried to do all of this at one point or another, and while vote-locking doesn't eliminate them it does make accomplishing them considerably slower and more labor-intensive for the griefer. I don't know if any of this factored into the original decision to implement it, but it wouldn't surprise me - and even if griefing wasn't a concern back then, I'd be very reluctant to remove the locks now because of it.

You must log in to answer this question.

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