8 ms·
The first two you listed were downranked by the flamewar detector. The last one was downranked by users. Admins didn't touch any of them. Note for everybody: c
by dang 3y ago
The first two you listed were downranked by the flamewar detector. The last one was downranked by users. Admins didn't touch any of them.
Note for everybody: can you guys please include the HN /item link if you're mentioning specific threads? That would be much more efficient and that way I can answer many more of people's questions.
- jeremyjh 3y agoThe flags on the last item don't seem to be made in good faith. This looks like abuse of the flag system to me. Is there a system for monitoring flag abuse?
- deleted 3y ago[deleted]
- comex 3y agoBy "the last item" you're referring to "Avoid Async Rust at All Cost", right? Personally I don't think that's abuse; I would have flagged that post if I'd seen it. That's despite the fact that I agree with a lot of what's in the post. The title is just too inflammatory. And there are more inflammatory bits in the post, such as saying the feature is "objectively bad", and saying that a community member's post "gracefully omits" some information (where the word "gracefully" sounds like an accusation that they were being disingenuous). Totally unnecessary. Chop off the inflammatory bits and you'd have a perfectly good blog post making an interesting point, but as-is that post was not going to lead to a productive discussion.
- nottorp 3y agoOf course, it's only inflammatory because async is a darling to more than half of HN :) But if we get into that we'll trigger the flame war detection.
- dang 3y agoI assume you mean this one: Avoid Async Rust at All Cost - https://news.ycombinator.com/item?id=39102078 https://news.ycombinator.com/item?id=39102078 - Jan 2024 (62 comments) I can make an argument either way there. The argument in favor of flagging it could be: Rust is one of the most-discussed topics on HN; Async Rust in particular has had a ton of discussion [1], including a major thread just a few days earlier [2] - therefore this post was very much in the follow-up category [3]; the article was arguably rather low-quality, especially by the standards of this much-discussed topic; its title was flamebait and arguably misleading as well since the article seems more about async in general; and generally it was more of a drama submission on a classic flamewar topic than an interesting technical piece. I'm not saying all that is fair but it's easy to imagine good-faith users flagging for such reasons. I checked the flagging histories of those users and only saw two cases where a user had previously flagged a different article about Rust, and one was years ago. For typical examples of other stories that the same users had flagged, see [4] below. A few of those might be borderline calls but I don't see abuse of flagging there. It's important to remember that even when a story is on topic for HN, flags are legit if the story has had a large amount of discussion recently. Otherwise HN would consist of the same few discussions over and over, and we have enough of that as it is! > Is there a system for monitoring flag abuse? There are some software protections in place against that, but like all such protections, they don't catch all the bad cases and they have false positives as well. We review the flags and turn flags off sometimes. I would not say it's perfect because although we try to look over all the flagged stories, it has to be done hastily (or one wouldn't get much else done). That makes it easy to miss things. However, users often email us at hn@ycombinator.com when they think a story has been unfairly flagged, and in those cases we always take a closer look. I don't know what percentage of the time we turn flags off in such cases, but it's not a low number. So if we include "users sending emails" as part of "the system", then yes, there's a system for monitoring flag abuse. Last point: this is a pretty typical case. I'd say it's borderline but in the end I probably agree with the flaggers. If the topic of Rust (and async Rust in particular) weren't already so thoroughly covered, and/or if the flamewar aspect hadn't been there, then I'd probably disagree with the flaggers. --- [1] https://hn.algolia.com/?dateRange=all&page=0&prefix=true&query=async%20rust%20comments%3E10&sort=byDate&type=story https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que... [2] https://news.ycombinator.com/item?id=39061839 https://news.ycombinator.com/item?id=39061839 - the word 'async' appears over 200 times in that thread! [3] https://hn.algolia.com/?dateRange=all&page=0&prefix=true&query=follow-up%20downweight&sort=byDate&type=comment https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que... [4] You Don't Have to Be a Jerk to Succeed - https://news.ycombinator.com/item?id=39228231 https://news.ycombinator.com/item?id=39228231 - Feb 2024 (21 comments) Birth rates are falling in the Nordics. Are natalist policies no longer enough? - https://news.ycombinator.com/item?id=39191651 https://news.ycombinator.com/item?id=39191651 - Jan 2024 (151 comments) New tires every 7k miles? Electric cars save gas; tire wear shocks some drivers - https://news.ycombinator.com/item?id=39175675 https://news.ycombinator.com/item?id=39175675 - Jan 2024 (64 comments) Google layoffs: Tech giant to cut down 30k jobs, says report - https://news.ycombinator.com/item?id=38791297 https://news.ycombinator.com/item?id=38791297 - Dec 2023 (6 comments) Code will make me rich and famous - https://news.ycombinator.com/item?id=38336699 https://news.ycombinator.com/item?id=38336699 - Nov 2023 (2 comments) The NSA Invented Bitcoin? - https://news.ycombinator.com/item?id=37599194 https://news.ycombinator.com/item?id=37599194 - Sept 2023 (61 comments) Leaving the Web3 cult - https://news.ycombinator.com/item?id=36803267 https://news.ycombinator.com/item?id=36803267 - July 2023 (47 comments) How the Military Is Using E-Girls to Recruit Gen Z into Service - https://news.ycombinator.com/item?id=36471105 https://news.ycombinator.com/item?id=36471105 - June 2023 (97 comments) Alphabet plans to announce its new general-use LLM called PaLM 2 at Google I/O - https://news.ycombinator.com/item?id=35866435 https://news.ycombinator.com/item?id=35866435 - May 2023 (5 comments) Is your husband/ boyfriend gay? LGBTQ - https://news.ycombinator.com/item?id=35734086 https://news.ycombinator.com/item?id=35734086 - April 2023 (0 comments)
- jjtheblunt 3y agoHN ID? I don't see that in the FAQ, maybe it's defined elsewhere? edit: oh duh. thanks all, answer was 'right under my nose'!
- arethuza 3y agoPresumably its the id parameter in the URL?
- jdminhbg 3y agoThe url for this page is https://news.ycombinator.com/item?id=39230513 https://news.ycombinator.com/item?id=39230513 so the id is 39230513
- Moru 3y agoMost likely in the URL, id=3923
- dang 3y agoI changed my comment to say 'link' instead of 'ID' so everyone can follow the same links. Thanks _kst_: https://news.ycombinator.com/item?id=39232594 https://news.ycombinator.com/item?id=39232594
- throwaway665544 3y agoIf you have nothing to hide, why not make all story and comment removal history publicly visible, like Wikipedia edits.
- skeaker 3y agoJust enable showdead if you want to see all of that. It's 99% botspam.
- krapp 3y agoThat would create one more thing for people here to complain about. People here would just accuse the mods of faking the mod log to hide their "real agenda" whatever that is.
- jethro_tell 3y ago[flagged]
- paulnpace 3y agoWikipedia can and does vaporize edits.
- formerly_proven 3y agoI don't think revdel can actually fully delete a revision, there's always at least a revision entry left, perhaps with no user name or summary.
- dang 3y agoThat would create a bureaucratic nightmare for no significant gain. Edit: see https://news.ycombinator.com/item?id=39234189 https://news.ycombinator.com/item?id=39234189 for a longer answer; and also krapp's comment at https://news.ycombinator.com/item?id=39232795 https://news.ycombinator.com/item?id=39232795, which makes a similar point.
- deleted 3y ago[deleted]
- jader201 3y ago> The first two you listed were downranked by the flamewar detector. Just some feedback that I've found a number of articles fall off the FP due to the flamewar detector that I've felt were good articles/discussions. In fact, I think some of the more valuable discussions tend to have a lot of back and forth discussions relative to the votes. But I also recognize that flamewars can also look a lot like that. So I'm wondering if it may be worth revisiting the algorithm for this, and maybe having it factor in a few other things vs. simply the vote:comment ratio (which is what I'm understanding it currently is, but correct me if I'm wrong). I don't think it necessarily needs to be a lot more complex, maybe simply add to it some standard deviation of upvotes/downvotes (or just a simple ratio), if that's not already part of it. But I've seen some discussions fall off that I don't remember seeing a particularly toxic discussion happening (e.g. relatively little to no downvoted comments). Again, happy to see flamewars fall off, but just hoping to see some more interesting/helpful discussions not get caught in the crossfire.
- dang 3y agoAbsolutely. We review the list of stories that set off that software penalty and restore the ones that are clearly not flamewars. No doubt we miss a few, and also - not everyone interprets these things the same way. But if you (or anyone) notice a case of a good thread plummeting off the front page, you can always get us to take a look by emailing hn@ycombinator.com.
- MichaelZuo 3y agoThere should be some way of doing language detection to detect the relative quality of 'flaming' going on. So the highest quality 'flame wars' can remain untouched, but downranking everything else below that bar probably makes sense.
- dang 3y agoYes, the carrot of automation would be so much easier than the stick of manual review. I haven't seen any system that works well enough yet though. The nice thing is that the comments are all public so if someone wants to take a crack at building a state-of-the-art sentiment detector or what have you, they can have a go—and if anyone comes up with anything serious, we'd certainly like to see it. As would the entire community I'm sure!
- _kst_ 3y agoOr include the URL rather than just the HN ID so readers can follow the links.
- dang 3y agoyes! good point. Edit: I changed my GP comment to say "link" instead of "ID".
- deleted 3y ago[deleted]
- caymanjim 3y agoHow can users downrank headlines? I only have an option to upvote them. While it's not too frequent, there are things that make it to the front page that I'd like to express my disapproval of.
- dang 3y agoUser flags, once they've accumulated above a certain threshold, have a downranking effect. Pretty sure this is in the FAQ: https://news.ycombinator.com/newsfaq.html https://news.ycombinator.com/newsfaq.html.
- caymanjim 3y agoI'm curious why there's no actual downvote for submissions. Was that ever discussed on here? I did a quick search for prior discussions on the topic but didn't find anything. To me, "flag" means "this is a serious violation that requires moderator attention". Something I'd want you to see and deal with because it's bigoted, illegal, spam, etc. I wouldn't flag something simply because I didn't think HN was the right audience, or because I personally dislike the topic. You seem to be encouraging me to use it simply as a downvote. I'm not going to start flagging things, nor do I feel that strongly about the lack of a downvote, but if flags are effectively downvotes behind the scenes, and if that's how users are treating flags (which they obviously are, from other comments on this thread), I think the UI should have a downvote button. I assume there's been discussion about this before and I'm curious about the thought process behind the decision. I don't find the FAQ to be informative about this.
- dang 3y agoThe only person who could answer that is pg because that design choice was part of the embryo of HN. He must have been thinking something though, because Reddit was originally his conception and he was an influence on the earliest development of Reddit as well (edit: and Reddit does have story downvoting - forgot to mention that bit).
- 3y ago
- kosolam 3y agoWhy don’t you make the system transparent? This will save you a lot of effort answering questions.
- kosolam 3y ago[flagged]
- eevilspock 3y agoPeople will game it. We don't need a transparent algorithm when we have transparent results, e.g. enable `showdead`, or the OP's project.
- dang 3y ago"Transparent" means different things to people, but if you mean a full moderation log: I think most likely it would produce more questions and effort, for no clear gain. I've written about this over the years: https://hn.algolia.com/?dateRange=all&page=0&prefix=false&query=by%3Adang%20moderation%20log&sort=byDate&type=comment https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu... Here's how I look at it: if trust is present, then we don't need to publish a full log, as long as we answer questions when people ask them. That degree of transparency has been available here for many years. If, on the other hand, trust isn't present, a moderation log won't create it. It will just generate more data for distrust to work with—and distrust always finds something. Thus our focus is on building trust with the community and maintaining it. That happens through lots of individual and group interactions, answering questions whenever we get them, in the threads or by email. That's what I spend most of my time doing. We're never going to take the community's trust for granted because it's what gives HN the only real value it has, and it would be all too easy to lose. But I would tentatively say that this approach has proven to work well for most of the community. If people learn they can always get a question answered, that's a powerful trust-building factor. Equally clear is that it does not work for everybody; but that's always going to be the case no matter what we do. I don't mean that we dismiss such users' concerns—quite the contrary, I make extra efforts to answer them. I'm just not under any illusion that we can satisfy everybody. It's satisfying enough if a few people can occasionally be won over in this way—which does happen sometimes!
- johnnyanmac 3y agoI don't necessarily want to dissect every little story, but this post was a funny edge case: https://news.ycombinator.com/item?id=39203106 https://news.ycombinator.com/item?id=39203106 a tame story that got some discussion, but was marked as a dupe. But I didn't see any other posts linked in the comments as expected. I search for other submissions and see two other posts... with 0 comments: https://news.ycombinator.com/item?id=39190710 https://news.ycombinator.com/item?id=39190710 https://news.ycombinator.com/item?id=39186297 https://news.ycombinator.com/item?id=39186297 I don't really have a critique or solution here, I imagine false negatives are an inevitability. Just sharing.
- dang 3y agoWe try to, and often users help by, posting links to the previous discussions in the thread. But there isn't enough time to do that in all of them. In this case, you can see from https://hn.algolia.com/?dateRange=all&page=0&prefix=true&query=Japan%20floppy&sort=byDate&type=story https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que... that there had been a lot of submissions, and from https://hn.algolia.com/?dateRange=all&page=0&prefix=true&query=comments%3E0%20Japan%20floppy&sort=byDate&type=story&storyText=none https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que... the ones that got comments. Of those, https://news.ycombinator.com/item?id=39165981 https://news.ycombinator.com/item?id=39165981 had been just a few days earlier. And it turns out that there actually was a link to it in the later thread: https://news.ycombinator.com/item?id=39204186 https://news.ycombinator.com/item?id=39204186, but this comment was flagkilled, probably because of the personal swipe in it. (You can still see it but only if you turn on 'showdead' in your profile.) I could go on! because there's endless detail one can go into about these calls. But you "didn't necessarily want to dissect every little story" :)
- johnnyanmac 3y agoAhh, that would explain it. Showdead is off on my account and I guess I didn't find every result on my end. That's a shame. But thank you! > could go on! because there's endless detail one can go into about these calls. But you "didn't necessarily want to dissect every little story" :) Yeah, i imagine if I went down every tiny rabbit hole it'd be a full time job. I'll leave that to the professionals haha.
- TheCoreh 3y agoThanks for replying with added context, didn't really mean to add more to your plate with this!
- dang 3y agoNo problem! I see these threads as opportunities to explain things to the entire community so I try to make the explanations as thorough as possible, and to answer every question that I see. (though I'm sure I don't see them all - if anyone has (or sees) a question that didn't get answered, you can always let me know at hn@ycombinator.com)