3 ms·

It's exactly as e12e describes: if you've had the page open for a while, and click an upvote, then the arrow disappears and it looks like you have voted. But i

by hyp0 12y ago

It's exactly as e12e describes: if you've had the page open for a while, and click an upvote, then the arrow disappears and it looks like you have voted. But if you refresh the page, you'll see that the arrow is still there. If you upvote now, on this fresh page, the upvote is counted - you can tell, because if you refresh the page now, the arrow will be gone. (This proves to me that I haven't been disenfranchised or banned in some way - I can vote, it just has to be on a fresh page.) I get the same behaviour on both firefox desktop, and the stock android browser. Why not try it, and see if you get the same behaviour? Of course, I don't know the details of how HN implements voting - it just behaves as if the link expires in some way... For a regular link on HN, if you leave it too long, it will explicitly say "link expired". But for upvotes, you don't see that message (presumably it is what gets returned to the up arrow though).

kogir 12y ago
Voting uses a completely different mechanism. There is no saved state or time component. Unless your login cookie has expired, votes will count. Can you tell if your browser actually makes the request? I'm going to try it with your comment, though I don't expect I'll be able to reproduce it. Update: Just tried it. Waited 1 hour, 36 minutes and upvoted your comment. Success.
- kogir 12y ago
  In fact, looking through our server logs, you've never voted more than once for the same item in the last 12 days. These are logs of all requests, before the code could even potentially error or filter them. For some reason, your browser isn't making the request, or it's getting dropped before we see it. If you have any ideas I'd love to hear them, but right now I've got nothing to go on.
  - hyp0 12y ago
    Thanks for looking into it. That does sound strange. My mobile internet connection is flakey at times; but unlike a regularly failed request, there isn't any evidence of failure for voting (BTW I noted that SO does give an alert if this happens for their votes.) I also tried it again and found sometimes it fails even on a "fresh" page (and as you've explained, that shouldn't make any difference anyway). It may have just been a coincidence when refreshing worked. I'm having a lot of network problems recently, so that may be it. But it's also definitely happened in the past, when I wasn't having any such problems. "The network is unreliable" - this would also explain why several other people have experienced this behaviour, that looks like expired links. Heh, probably the HN maintainers have great network connectivity, and so you mightn't ever see it yourself.

by hyp0 12y ago

kogir 12y ago

Voting uses a completely different mechanism. There is no saved state or time component. Unless your login cookie has expired, votes will count. Can you tell if your browser actually makes the request? I'm going to try it with your comment, though I don't expect I'll be able to reproduce it. Update: Just tried it. Waited 1 hour, 36 minutes and upvoted your comment. Success.

kogir 12y ago
In fact, looking through our server logs, you've never voted more than once for the same item in the last 12 days. These are logs of all requests, before the code could even potentially error or filter them. For some reason, your browser isn't making the request, or it's getting dropped before we see it. If you have any ideas I'd love to hear them, but right now I've got nothing to go on.
- hyp0 12y ago
  Thanks for looking into it. That does sound strange. My mobile internet connection is flakey at times; but unlike a regularly failed request, there isn't any evidence of failure for voting (BTW I noted that SO does give an alert if this happens for their votes.) I also tried it again and found sometimes it fails even on a "fresh" page (and as you've explained, that shouldn't make any difference anyway). It may have just been a coincidence when refreshing worked. I'm having a lot of network problems recently, so that may be it. But it's also definitely happened in the past, when I wasn't having any such problems. "The network is unreliable" - this would also explain why several other people have experienced this behaviour, that looks like expired links. Heh, probably the HN maintainers have great network connectivity, and so you mightn't ever see it yourself.