-19

Of what use is it to the community for someone to take the time to down-vote a question I posted because of two typos?

  • 8
    Why do you think that the typos caused the downvotes? Furthermore, we have no context since you haven't provided any links. Lastly, "downgrading" does not mean the same thing as "downvoting". – user392547 May 2 '19 at 4:16
  • 2
    A question completely riddled with typos and mistakes in grammar might well be downvoted. Especially if it's very long and is essentially impossible to read. That would make it a bad question. (And it would also likely be closed as unclear.) But it's highly unlikely (although not impossible) that just a couple of typos would result in a downvote. – Jason Bassford Supports Monica May 2 '19 at 4:41
11

I will bet you dollars to donuts that this didn't happen.

Not that I'm disputing your question was downvoted. That's plain for anyone to see.

What neither you nor anyone else can see is why someone downvoted a question, so I'm betting that it wasn't two typos that were the motivation behind the downvotes.

The tooltip on the downvote arrow contains an explanation of the reason(s) why someone might have downvoted your question:

This question does not show any research effort; it is unclear or not useful

If serious typos made a question unclear, then that would certainly be a valid reason to downvote. But it's extremely unlikely that two typos would cause that problem.

Unless, of course, you were asking a question on Stack Overflow, and the two typos were in code, and they were causing an obvious error, thus making the question neither useful to anyone else nor indicative of research effort on your part.

Either way, a downvote is meant to be a signal that there is something wrong with your post—that you should take another look at it, and see if there is something (or multiple somethings) that you can improve. If you've taken a couple of hard looks, and yet still can't find anything that can be improved, then you should just move on and ignore the downvotes. They're just expressions of opinion, after all.


So, I did some research, and I dug up the question you are probably referring to. That question was indeed downvoted, and indeed someone edited it to fix two typos. However, you have no way of knowing whether those two events were connected. You don't even know if it was the editor who cast the vote.

Well, you now know who cast the second downvote, but only because I'm telling you it was me. The question is completely off-topic for Stack Overflow. It has nothing to do with programming within the scope defined by our Help Center. Therefore, I have also closed it as off-topic. I'd also bet that its being off-topic is the reason why the first downvote was cast.

  • 3
    I knew it was you who down vote all those posts! – rene May 2 '19 at 7:28
  • I think it would be helpful if the person down-voting would be required to leave a comment as to why it was down-voted. Thank you for letting me know it was off topic, though. – Vietyank May 4 '19 at 2:43
  • Mandatory feedback on downvotes has been proposed many, many times. Here is a summary of why it is always declined. @Vietyank – Cody Gray May 4 '19 at 3:19
  • It would have saved all this chatter – Vietyank May 6 '19 at 0:06

You must log in to answer this question.

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