5 ms·
It looks like this "Show HN" post wouldn't have a high "gag" score [1], so either the post has been flagged multiple times (unlikely), or, most likely, the majo
by mrmaddog 14y ago
It looks like this "Show HN" post wouldn't have a high "gag" score [1], so either the post has been flagged multiple times (unlikely), or, most likely, the majority of those early votes came from the same location, causing the voting ring safeguards [2] to kick in.
[1] http://news.ycombinator.com/item?id=1782058 http://news.ycombinator.com/item?id=1782058
[2] http://news.ycombinator.com/item?id=3894695 http://news.ycombinator.com/item?id=3894695
- dazbradbury 14y agoUnfortunately, I know this wasn't the case - I didn't provide the link to anyone in our office, which has it's own IP, and I know they weren't aware of the HN post until afterwards. I also wouldn't publicly use this as an example if I knew I had been rigging the votes! So maybe it was just a case of HNers flagging the story as it became popular, as the title was fairly link-baity? I was under the impression that flagging a story kills it rather than suppresses it, but regardless, if that's the case then it makes sense. Edit: One comment in your example link by ColinWright seems to state 2 or more "flags" can cause this behaviour: http://news.ycombinator.com/item?id=3893207 http://news.ycombinator.com/item?id=3893207 If that's the case, it's probably best people don't know about it, as used maliciously it would be fairly disruptive.
- jtheory 14y ago> Unfortunately, I know this wasn't the case You can't know -- just because it wasn't in your office doesn't mean it didn't happen. One of the first readers to see it may have mass emailed his/her colleagues who all read/upvoted when they got into work in the morning, for example....