This is so very analogous to a real-life situation. You try to correct someone, with no real harmful intention, but then get some nasty feedback.
So what do you do?
Just write good answers/questions- that is the only way you can overcome this. A few downvotes will always be diluted in the upvotes. The number of people doing constructive work will always ...
Yeah, we do care about our posts. We do not take it lightly when we receive a downvote. We try to make the post better.
In the best case we have an explanation in a comment to help us what could be done. In the second best case we see for ourselves what we did wrong. In both cases we will not hesitate to improve our post with an edit, well knowing that ever ...
This is a response to the general question, and not specifically to the example. The whole Stack Exchange system is a bit complicated, so if the example involved a new or new-ish user, it was probably just an innocent mistake using the site, and not something for which anyone ought to be faulted.
I think threatening to downvote is a bad practice. If you ...
Voting on StackExchange sites is anonymous - even the community moderators do not have access to that information.
Try adding a comment to your question asking for feedback on how to improve the question.
Look for similar style questions - look at their content and see if you can add similar information to improve the question.
At the end of the day - ...
My question is which one is the better solution and also does the second answer need to be downvoted?
Not at all, no.
I save downvoting for things that are unhelpful, incorrect or just plain don't belong there as an answer. Just because it's another answer doesn't mean it's any less helpful to somebody else and it doesn't mean somebody else should lose ...
Yeah some things look right (so attract votes for effort) but are technically incorrect. It happens to anybody who answers enough on the site.
There are things you can do that are genuinely useful:
Leave a comment. Explain what is wrong and why. Be technical. This lets the poster and other potential voters know. They can fix it, or even explain why they ...
The correct way is to vote based on the content.
Is it a good question? - Vote it up.
Is it a bad question? - Vote it down.
Don't just vote to counter down-votes.
There are two problems with flagging a question for moderator attention because of a down-vote.
A moderator should not be there to judge a down-vote and invalidate it if he thinks it was not ...
The main rule of thumb I would use is to ignore the fact that you answered it, and use regular downvoting rules depending on how you downvote. In one sentence:
If you hadn't answered it, would you downvote?
Especially, you shouldn't downvote early to get your answer up for the OP and others to vote on more, and you shouldn't do this just out of jealousy ...
Thanks for posting the solutions you found to your own problems. This is a great thing to do and the site has some ways of encouraging it - for example, this little message next to the checkbox to post your own answer seems quite inviting to me:
Even more encouragingly, we have this badge
I probably spend more time than most users looking at self-...
What Zanna said is 100% correct and self answers are encouraged but the down votes have nothing to do with self answers, as the questions were voted up.
Let's look at your answers
Dell Inspiron does not go into GRUB after shutdown from Kubuntu
I think I found the answer. I disabled to Legacy ROM option in the
BIOS settings while leaving UEFI enabled. ...
Here's my take on the four. Remember that both presentation and content of a question matter; as Nick commented, most of us have a life outside of AU and cannot spend a lot of time trying to pin down the essence of a very poorly phrased or unnecessarily long question.
Ubuntu and Windows 7 on 1 Tb hard
Notice the title, which is why the question probably ...
I just vote to close.
The site offers a duplicate search, some users use it, some don't. Sometimes if you notice a trend, you can do a search for a common duplicate and then just flag a bunch at once.
For example I do a search for "black screen" and "freeze" on occasion and always find some getting through. Just keep flagging them! The only time I ...
Because, reiterating Oli's words, there's no need to prevent users from "gaming the system by downvoting other question", as there's no point in downvoting other questions to your advantage, unless your aim is for your question(s) to be the highest scoring ever question(s) on the site.
Downvotes do not in any way prevent people from improving their posts.
Downvotes have no effect on how easily a post may be edited.
And when a post is edited, this enables voters to change their votes. (They can also change them for a short time after casting them, to help people correct mistakes.)
Furthermore, a new user starts out with 1 reputation, and ...
There is effectively no hard limit, but it's probably not useful to have one.
The system does not attempt to impose any particular limit on how low a post's score can go. It probably cannot go lower than -2,147,483,648. But in practice, it is extremely unlikely that any post will ever receive billions of downvotes! The number of users on the site who have ...
Why shouldn't there be? There are badges for all other major moderation tasks (flagging, editing, upvoting, deleting, reviewing), why should downvoting be exempt? Whatever you may think of it, downvoting is an important part of Stack Exchange.
I've looked into this and have determined the culprits.
This will be dealt with overnight by the serial voting reversal mechanism - so just hang-on tight.
As to the culprits - they will be suitably dealt with once the votes have been invalidated.
Typically, I prefer using comments as well. Voting up/down sort of sends the wrong message to new users, even though as Zanna explained it is not intended to be a form of punishment/reward, but people see it that way. Well, OK, maybe it actually is intended. Stack Exchange is sort of built on the game principle to retain users; to quote Jeff Atwood - one of ...
To me, the bottom line has always been:
Does it answer the question?
If the project directly answers the question, I really don't care if the person writing the answer and the person writing the application are one and the same. I don't even care if the person is selling the app.
Now, there are a few things to keep in mind:
The person writing the ...
Agree 100% with @muru. The only thing I'ld add is that downvoting is arguably even MORE important than upvoting in the answer sorting process. There's also a badge for retracting a negatively received post/answer.
I have, in the past for example, gone through and started deleting all my 0 or negative answers or questions as site cleanup assuming there's ...
Voting is really important on Stack Exchange sites and its purpose is often misunderstood. The purpose of voting is not
to reward users with unicorn dollars1
to punish users by taking their unicorn dollars away
to encourage users
to discourage users
Votes have the above effects and we should not ignore those effects. But the primary purpose of voting is to ...
Closing a question as off-topic or not a real question gives it an automatic downvote (the downvote is recorded as by the Community user).
There is nothing wrong with a bad question being downvoted. You should never upvote a question just to compensate: upvote only if you think the question deserves an upvote.
If the question is reopened, the automatic ...
Well I've given you an answer.
Most "why isn't this the case" questions are probably viewed as being argumentative or a feature request, neither of which are thread types we really support here. We're primarily here to solve problems and those sorts of questions sometimes just don't have atomic answers.
You should take a down-vote as the need to give an answer some attention. Courteous down-voters will tell you what the problem is and (assuming they're right, they might not be) that'll let you know if you should be deleting or improving your answer.
Unfortunately there aren't always comments and you have to use your own judgement. If you can't decide, feel ...
Reasons a post could be downvoted include, but are not limited to:
Somebody hates you.
The user who downvoted always downvotes on the first Thursday of every month.
Someone misunderstood your answer.
Someone dislikes your avatar.
Someone hates bash, why are you using bash?
Someone is having a bad day
Your answer has errors.
You left a comment ...
Yes, it is fine to comment before you downvote, even have a full conversation before you make up your mind.
I will often leave a comment suggesting fixes before casting a vote, it gives to OP chance to respond and fix their post. Some will respond and some won't, so pin the tab, give it 24 hours and come back.
Sometimes, it will be a user's response or ...
Short answer: no.
Long answer: no.
It is never okay to threaten anyone with downvotes or similar measures, because in general threats are not accepted in the community, and downvotes are not to be used for this purpose. In this particular case however, I think you misunderstood what the person was saying.
They seem to be suggesting that if the answerer ...
I would disagree. These questions are often duplicates of more-obvious canonical ones, which may be more general, but do solve the problem. By looking at the mouseover text of the downvote button, you will see that it states:
This question does not show any research effort; it is unclear or not useful (click again to undo)
and since a search on AU or ...