Comment by lbrito
20 hours ago
I get the irony, but its a bit meaningless since we can't compare the quantity of these (yet) uncensored posts with those that have been taken down, and thus aren't visible.
More importantly, other commentors here have already admitted to flagging this entry. The way flagging exists now rewards one-sideism and partisan behaviour - all it takes is a relatively small group of discontented people to take down a story that is otherwise interesting to the vast majority of posters. A counter-flag option would balance things.
> all it takes is a relatively small group of discontented people to take down a story that is otherwise interesting to the vast majority of posters.
That's not accurate, because if a story is interesting to the vast majority of users, it will get lots of upvotes—and lots of upvotes is enough to defeat a small number of flags. In that sense, we already have the counter-flag option you're arguing for.
That's good to know, thank you for the explanation.
Stories don't always get the chance to gather the sufficient amount of up votes before being nipped in the bud by dissatisfied flaggers though, depending on the time of day. Some of them, like https://news.ycombinator.com/item?id=46357887, clearly had great interest here and got a large number of upvotes that was, nonetheless, insufficient to prevent the flagging.
That's true. Then again, however, if a story is important enough to the community, it will get reposted—sometimes many times, either with the same URL or a different one. It's not so easy as people assume for flags to suppress that kind of story.
The submission you linked to (https://hn.algolia.com/?dateRange=all&page=0&prefix=false&so...)
What was the ratio of upvotes to flags when this thread was taken down last night?
What do you mean by taken down?
2 replies →