Bots. I've posted many popular and unpopular takes here. Down always comes first, and as the bot votes evap into the ether, the true human take is almost always revealed after an hour or two.
If you change `how=up` to `how=down` it downvotes the post.
I tried it once, didn't change the vote count, but I issued the inverse operation with `how=un` and the vote count went up, so I'm guessing someone upvoted at the same time I downvoted. That or it doesn't really work like it says it does, but it does respond with a 301 followed by an OK, so I think this works.
I tried this and had no change with either down or the subsequent un, using my own upvote link's token.
Perhaps someone coincidentally upvoted the post at the same time you attempted to undown the submission, rather than upvoting when you attemped to downvote it.
As I understand it, -4 is the lowest you can get (basically everyone hates your point of view), so you may have found a bug but more likely found 5 or so people who don’t like you quicker than expected!
I have seen (my) posts bounce up and down so there I suspect there is a lot of
Voting going on compare to actual movement. But in the end HN is biased for positivity (as you cannot go lower than -4)
But someone with sight of codebase might have more useful comments
On HN I almost never downvote. On reddit this was different. Not sure why but I feel that on HN karma is so much harder to get that I don't want to be an obstacle. On reddit I could more easily downvote. It also was easier to get karma. (Reddit is annoying with regards to its censorship though. That is one arbitrary censorship over there ...)
This reminds me, I've wanted to make a bot to automatically upvote the most downvoted posts in a thread with the HN api. I'd call it anti-echochamber.HN or something like that.
>Looks like we have a race condition that someone triggered by using a script to rapidly upvote and then unvote the submission. I'm not sure whether to be grateful or pissed. Perhaps I'll settle on grateful once I've fixed it.
>In the meantime, please don't anybody else do this!
19 comments
[ 3.1 ms ] story [ 47.1 ms ] threadDoesn't appear to be negative anymore, but here is what it looked like: https://vale.rocks/micros/20260512-0652
Screenshot was taken at 06:50 UTC.
I suspect the same is happening for some others too, based on the comments on that article.
Bizarre!
Update: 2 minutes later and the link from the hn home page now correctly leads to: https://news.ycombinator.com/item?id=48106316
Never seen that happen before.
If you change `how=up` to `how=down` it downvotes the post.
I tried it once, didn't change the vote count, but I issued the inverse operation with `how=un` and the vote count went up, so I'm guessing someone upvoted at the same time I downvoted. That or it doesn't really work like it says it does, but it does respond with a 301 followed by an OK, so I think this works.
Perhaps someone coincidentally upvoted the post at the same time you attempted to undown the submission, rather than upvoting when you attemped to downvote it.
Here's a snapshot from when the count was 0 https://web.archive.org/web/20260512115623/https://news.ycom...
I have seen (my) posts bounce up and down so there I suspect there is a lot of Voting going on compare to actual movement. But in the end HN is biased for positivity (as you cannot go lower than -4)
But someone with sight of codebase might have more useful comments
Ha ha ha.
>Looks like we have a race condition that someone triggered by using a script to rapidly upvote and then unvote the submission. I'm not sure whether to be grateful or pissed. Perhaps I'll settle on grateful once I've fixed it.
>In the meantime, please don't anybody else do this!
https://news.ycombinator.com/item?id=48114191