> HN has a an automated simple proxy for flame-war detection. One characteristic of flame-wars is that people get into a to'n'fro over the issue, and the number of comments balloons. However, no one else is really interested, so they don't upvote the submisson, and the participants can only upvote a submission once, so the number of points doesn't increase.
> Result is that a simply proxy for a flame-war is the number of comments on a submission out-stripping the number of votes.
> A side-effect of that is that if there's a mildly interesting submission that lots of people comment on, but very few upvote, then the flame-war penalty will be triggered, and the submission will sink like a stone, never to be seen again.
> Scott and I get emailed every time that software trips so we can quickly look at which threads are being penalized and reverse the penalty when it isn't helpful. The only time we don't do that is when we're sleeping.
> We tend to call it the 'overheated discussion detector' these days, since it detects more than flamewars. However, that phrase is more awkward to say than 'flamewar detector'. If anyone can come up with a better name I'd love to hear it.
> Turning that software off is not an option, because HN would be overwhelmingly more dominated by flamewars if we did so. It's not primarily the individual threads that I fear, it's the systemic effects of having them be more dominant. HN exists most of all for the quieter, deeper, more out-of-the-way finds that would be the first to get excluded under such a regime. That would really be an existential risk to HN.
> Incidentally, that last point generalizes. When people complain that we don't do X, for some obvious X, it isn't because we don't value X (e.g. free speech or whatnot). It's because we're worried about systemic effects.
---
Quite simply said, the post and comments got overheated and looked like flame wars and so was pushed off the to have it cool down.
shagie|1 year ago
> HN has a an automated simple proxy for flame-war detection. One characteristic of flame-wars is that people get into a to'n'fro over the issue, and the number of comments balloons. However, no one else is really interested, so they don't upvote the submisson, and the participants can only upvote a submission once, so the number of points doesn't increase.
> Result is that a simply proxy for a flame-war is the number of comments on a submission out-stripping the number of votes.
> A side-effect of that is that if there's a mildly interesting submission that lots of people comment on, but very few upvote, then the flame-war penalty will be triggered, and the submission will sink like a stone, never to be seen again.
https://news.ycombinator.com/item?id=16020089
> Scott and I get emailed every time that software trips so we can quickly look at which threads are being penalized and reverse the penalty when it isn't helpful. The only time we don't do that is when we're sleeping.
> We tend to call it the 'overheated discussion detector' these days, since it detects more than flamewars. However, that phrase is more awkward to say than 'flamewar detector'. If anyone can come up with a better name I'd love to hear it.
> Turning that software off is not an option, because HN would be overwhelmingly more dominated by flamewars if we did so. It's not primarily the individual threads that I fear, it's the systemic effects of having them be more dominant. HN exists most of all for the quieter, deeper, more out-of-the-way finds that would be the first to get excluded under such a regime. That would really be an existential risk to HN.
> Incidentally, that last point generalizes. When people complain that we don't do X, for some obvious X, it isn't because we don't value X (e.g. free speech or whatnot). It's because we're worried about systemic effects.
---
Quite simply said, the post and comments got overheated and looked like flame wars and so was pushed off the to have it cool down.