18
$\begingroup$

I had noticed before that answers sometimes receive upvotes almost immediately, and had been wondering how the upvoter had been able to read and assess the answer so quickly, but so far there had always been at least something like $10$ seconds between the posting and the upvote.

However, today I posted this answer (now deleted), and I never got to see it without upvotes – by the time the page had loaded, the upvote counter already said "$1$". The page didn't take unusually long to load in my browser, so the upvoter must have loaded the page just when the answer appeared and then almost immediately clicked to upvote.

Now usually one might perhaps have thought that they had also been working on an answer and thus knew the answer, saw the correct result at the bottom and immediately clicked. That would still be somewhat negligent, since the rest of the answer might be wrong or misleading or badly written, but at least it would be acknowledging a correct result.

It just so happens, however, that the answer was completely wrong and didn't answer the question, since the question asked for the first moment and I (being a physicist) associated "moment of inertia" and calculated the second moment instead.

So this upvote was almost certainly not based on an appreciation of the answer; and that makes me think that some of those other surprisingly fast upvotes that I've seen in the past weren't, either.

Which raises the question: Who's doing this, and why, and how can we prevent it?

$\endgroup$
8
  • 7
    $\begingroup$ Isn't it possible that whoever upvoted your answer had the same misinterpretation of the question that you had? $\endgroup$
    – user856
    Commented Mar 3, 2013 at 21:05
  • 1
    $\begingroup$ @Rahul: It's certainly possible, but that was just an additional aspect that makes it even less likely -- I'd already started writing this question before the OP pointed out my mistake, because even without that it just seemed too fast. I literally never saw the $0$ on the upvote counter. I'm surprised even that someone could click that fast, even without glancing at the answer. And even if they did have the same misinterpretation and did somehow manage to load, glance and click all in a second or two, it would still be unfortunate that answers are upvoted without being read even cursorily. $\endgroup$
    – joriki
    Commented Mar 3, 2013 at 21:18
  • $\begingroup$ It'd be natural to suspect me based on my answer here. But rest assured that I (a) neither read nor upvote calculus-type answers; (b) do read the answers that I upvote. $\endgroup$
    – user53153
    Commented Mar 3, 2013 at 21:35
  • $\begingroup$ I wonder whether the server end of the SE software allows a rogue client to vote for a question number before a question to go with that number even exists. That would seen to be necessary to explain your upvote-on-the-first-pageload observation. $\endgroup$ Commented Mar 4, 2013 at 5:44
  • $\begingroup$ (Well, there's a window of time between when the server replies to your post with a redirect and when your browser requests a new page load, during which an upvote could theoretically arrive. That would be at most a few hundred milliseconds, during which someone else would need to have received a fresh pageload and sent a vote back to the servers.). $\endgroup$ Commented Mar 4, 2013 at 5:51
  • 12
    $\begingroup$ #highrepproblems $\endgroup$
    – Alexander Gruber Mod
    Commented Mar 4, 2013 at 6:16
  • $\begingroup$ Essentially the problem is "how do we prevent people from upvoting before we think they have properly evaluated the question," which seems to be an intractable problem fraught with subjectivism, to me. (Unless, of course, there really are some voting shenanigans going on...) $\endgroup$
    – rschwieb
    Commented Mar 4, 2013 at 19:59
  • $\begingroup$ This is what I have seen many times at this site. $\endgroup$
    – Mikasa
    Commented Mar 11, 2013 at 16:08

3 Answers 3

16
$\begingroup$

Voting on the site is not necessarily based on mathematical content. Many times people vote out of "loyalty" or "appreciation" for a user. I know that sometimes I do that as well, when I see a user which consistently writes good answers I will usually vote his/her answer before reading it fully. Why? because I know that the probability that the answer is going to be great is very high. Rarely I am mistaken, in which case I may decide to undo my vote.

Certainly it sounds very reassuring that people will tell you that "they only vote answers they read", but in a site this big it's not true anymore. Voting has to do with the mathematical content, but it's still not 100% correlated with it.

I do believe that this happens only with well-established users that wouldn't get there without writing a lot of good answers to begin with. But I don't know about that, and we'll probably never know until voting habits are made public.

$\endgroup$
5
  • 4
    $\begingroup$ (+1) but myself, I'd change "until voting habits are made public" to "unless voting habits are made public". $\endgroup$
    – robjohn Mod
    Commented Mar 3, 2013 at 23:41
  • 1
    $\begingroup$ Along these lines, here is a strange case: math.stackexchange.com/questions/317110/… In this case, there are 2 answers, one of which I provided. I believe my answer addressed the OP's concerns and correctly provided a path to a solution - as well as the solution for good measure. The OP accepted the other answer, however, despite the fact that it provided a poorly-thought out hint that led nowhere. My requests to show how this solution would work went unanswered. So, yes, I understand the concerns here. $\endgroup$
    – Ron Gordon
    Commented Mar 4, 2013 at 1:16
  • 2
    $\begingroup$ @rlgordonma Note, however, that your answer got upvoted more than the accepted one, which means the voters exercised better judgement than the OP. I had a similar case here. This seems to be a trend: when voters see that the best answer was not the one accepted, they "compensate" with extra votes for the non-accepted answer. $\endgroup$
    – user53153
    Commented Mar 4, 2013 at 1:39
  • $\begingroup$ @5pm: Yes, over the long haul, that is true, for which I am grateful. But in the short term, it was not the case. Thanks for posting your case, I see what you mean. $\endgroup$
    – Ron Gordon
    Commented Mar 4, 2013 at 1:44
  • 7
    $\begingroup$ +1 ... now I will read the answer. $\endgroup$
    – Neal
    Commented Mar 5, 2013 at 16:41
8
$\begingroup$

It is hard to impose any sort of conditions on the way people vote. Some votes seem very well thought out and others seem random and even counter-intuitive.

In the end, all one can do if votes seem questionable, is to ask the voters for their reasoning. This may get replies and it may not, but I don't see that much else can be done.

$\endgroup$
6
  • 3
    $\begingroup$ I suppose one could jiggle the software so that no upvotes are accepted until 10 seconds after the page is opened (or $n$ seconds, where $n$ is the length of the answer, in lines). I don't know that I'd be in favor of doing that; I'm just saying that I suppose it could be done. $\endgroup$ Commented Mar 3, 2013 at 23:09
  • $\begingroup$ @GerryMyerson Sounds like a good idea. The comment votes are already timed (must be 5 seconds apart), and the buttons in review queues do not become available at once on page load. Having the same behavior of vote buttons would make sense to me. $\endgroup$
    – user53153
    Commented Mar 4, 2013 at 6:47
  • $\begingroup$ @5pm, feel free to make a feature request on metaStackOverflow or wherever it is that these things are discussed. $\endgroup$ Commented Mar 4, 2013 at 12:47
  • 1
    $\begingroup$ @GerryMyerson It seems that there already was a feature request along those lines (although the poster was more concerned about downvotes). As you can see, it did not receive much support (the score is -24). $\endgroup$ Commented Mar 6, 2013 at 21:44
  • $\begingroup$ @Martin, some of that $-24$ may have had to do with the poster's attitude and the specifics of the downvote about which the poster complained, but I take your point. $\endgroup$ Commented Mar 6, 2013 at 23:09
  • 1
    $\begingroup$ (I cooled down to the idea of software-imposed delay. If someone wants to vote without thinking, they will do exactly that, only 10 seconds later.) $\endgroup$
    – user53153
    Commented Mar 8, 2013 at 4:25
7
$\begingroup$

The style in which an answer is written and the author of the answer can both be used to make inferences about the extent to which an answer is correct and/or useful without thoroughly understanding it. Obviously neither of these is foolproof, but then again neither is thoroughly understanding an answer. Imperfect feedback is still probably preferable to very little feedback (which to me is the most likely consequence of requiring a more rigorous standard for upvotes, even assuming that we could implement such a standard).

$\endgroup$
8
  • 1
    $\begingroup$ There was no time to assess the style in which the answer was written. I'd actually be surprised if there was even time to glance at the author or the final result for a second, but certainly nothing less trivial than that. Since I never saw the zero upvote count, the time the upvoter had was at most the difference between the times it took our browsers to load the page, and mine wasn't being particularly slow, so it was a matter of fractions of a second, at most a few seconds. $\endgroup$
    – joriki
    Commented Mar 3, 2013 at 23:47
  • $\begingroup$ @joriki: a few seconds is usually how long I take to decide whether to upvote or downvote an answer. $\endgroup$
    – Qiaochu Yuan Mod
    Commented Mar 4, 2013 at 0:10
  • 1
    $\begingroup$ But that doesn't really explain Joriki's observation. When he presses the "Submit" key, the servers more or less immediately start serving his browser a freshly rendered question page, complete with the vote total for his new answer. Why would the server wait until it had shown the answer to some other user, and that user sent back a vote? Even if somone used a bot to upvote the answer without human interaction, his vote would not reach the SE server over the network until the initial render was already sent to Joriki. There should be no way he'd see an upvote_on the first pageload. $\endgroup$ Commented Mar 4, 2013 at 5:41
  • 3
    $\begingroup$ @Henning I think vote totals on the question page are fetched separately from the static page elements, they change without a page reload. So it's possible that during the time it took to render the page in joriki's browser the script responsible for the vote count fetched updated information. $\endgroup$
    – user53153
    Commented Mar 4, 2013 at 6:53
  • 2
    $\begingroup$ @5pm: I've never seen them change spontaneously, and they are present in the raw HTML response from the original page load (checked with wget). $\endgroup$ Commented Mar 4, 2013 at 7:05
  • 3
    $\begingroup$ @HenningMakholm The count is present in HTML, but it also gets live updates via WebSocket, if your browser supports it. I saw it happening more than once, and some quirks of this feature were discussed on meta.SO here and here. $\endgroup$
    – user53153
    Commented Mar 5, 2013 at 3:34
  • 3
    $\begingroup$ I am totally ignorant about the inner workings of the SW, but I have seen the upvote count change spontaneously. $\endgroup$ Commented Mar 5, 2013 at 10:11
  • 1
    $\begingroup$ @joriki: I'd be curious, whether there is some option, that the half(?) automated "mirrors" at some foreign hosts could manage to upvote automatically based on some contents or user or some other fancy stuff... $\endgroup$ Commented Mar 5, 2013 at 13:00

You must log in to answer this question.

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