Please don't. Voting on a post should have absolutely nothing to do with who wrote it or its current score and entirely to do with its current content.
If you want to reward an answer that went above and beyond, you can offer a bounty. There is an existing bounty reason to "reward an existing answer".
I can answer from my own experience here. I think I've asked one question which proved to be a duplicate, and I think the reason for my mistake was that I don't know how to read Hebrew, and I'm not familiar with the technical terminology.
If you only read English, and if you don't know the proper terminology, it is difficult to sort out which questions ...
First, here is what the documentation says about downvotes:
When should I vote down?
Use your downvotes whenever you encounter an egregiously sloppy, no-effort-expended post, or an answer that is clearly and perhaps dangerously incorrect.
What does that mean with respect to duplicate questions? Each user will evaluate this a little differently, but here ...
Starting in the next build, 10k+ users will be able to see all of their votes from the appropriate sub-tabs of their profiles.
From the Dave Haney, the dev who implemented this:
I've modified the code so that 10K users can see votes on (un)deleted posts under the appropriate tabs (deletion, undelete) of the votes section of their profile. This will be ...
The total number of votes per candidate is released publicly at the end of the election (as a BLT file) and anyone can even run the Meek-STV themselves to verify the winner. When ready the file should be at https://judaism.stackexchange.com/election/download-result/2
Here is the output from the last election.
As noted by various commenters, there is no way to see why one was (or who) downvoted. See this meta post for more details. Generally speaking, downvoters are encouraged to leave comments explaining themselves, but no one can make them do that.
Often times, the downvoted party will leave a comment asking for clarification, but in situations like this (...
The most successful search engine (and possibly most successful company period) agrees - rank importance by the importance of those who give it importance.
The logic behind this is the same logic that gives reputation in the first place - the community trusts your opinion. So you are granting trusted users the ability ...
Yes, it should be a factor in the decision.
Closing for duplicate is a special case - there is no reason to avoid upvoting the question, or closing a highly upvoted question in that case. The duplicate question could be better asked than the original and worthy of upvotes and attention, which lead people to the other question to actually post answers. That ...
After all these votes indicate that the topic is of interest.
Unfortunately, interesting, does not an on topic question make.
To borrow from this excellent answer: the cons of letting an off topic question through even if it is upvoted include:
.. the noise of a non-technical non-helpful question.
.. and the bad precedent that confuses new users about what ...
So my vote on an answer about, say, the Ramban (don't know much, but not totally ignorant so might vote sometimes) should be based on the reputation I've earned from answers about, say, Shabbat (about which I know rather more)? And even if you somehow did it based on tags, some tags are pretty broad and it wouldn't be much more meaningful (e.g. halacha).