Looking at the list of removed stories makes me really happy with the moderators here. They're all sensationalist, advertising for some company, clickbait, way off topic, or some combination of above. In fact, I don't see a single story that I personally feel should not have been removed.
Thanks, mods.
At a quick glance, I found several that don't match that criteria you mention, here are a few:
Open Source Doesn't Require Providing Builds
https://codeengineered.com/blog/2024/open-source-not-builds/
Sam Altman Says AI Using Too Much Energy Will Require Breakthrough Energy Source
https://futurism.com/sam-altman-energy-breakthrough
Avoid Async Rust at All Cost
https://blog.hugpoint.tech/avoid_async_rust.html
(Perhaps that last one could be renamed to be less hyperbolic, but the content was still an interesting opinion piece)
I don't think this is being done by the mods, by the way. It's more likely some spam filter with false positives, report brigading, or an anti upvote ring mechanism.
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.
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.
Absolutely. 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.
There 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.
Yes, 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!
You don’t really need a state-of-the-art anything here. People get too distracted with building the perfect system when it comes to use cases like this because they are paralysed thinking about the avoidance of false positives and make a bunch of sub-optimal decisions on that basis. False positives are much less of a problem with a human in the loop, and putting a human in the loop doesn’t require moderator effort.
You can probably put a big dent in the number of low-quality comments by just showing a “hey, are you really sure you want to post this?” confirmation prompt and display the site guidelines when you detect a low-quality comment. That way you can have a much more relaxed threshold and stop worrying about false positives. Sure, some people will ignore the gentle reminder, but then you can be more decisive with flags and followup behaviour because anything low quality that has been posted will by definition already have had one warning.
You're right about one thing: I didn't need to say "state of the art". A system that works at all would be great!
I don't think a confirmation prompt will help because people tune such things out after they've seen them a few times.
I hate myself for saying it, because of all of the buzz/hype, but LLMs can assist here.
You get better intent assessment than with NLP/ regex/whatever.
Plus HN is entirely in English, so you never have to worry about lexical resource gaps.
There is no off the shelf solution - afaik. In addition I have no idea how expensive running costs will be.
But something serviceable can be built.
Source: mod /t&s person dealing with these things
Even a bad implementation isn’t going to be showing this warning to people often enough to desensitise them. And if they make a habit of ignoring the warning to post flamewar stuff… that’s solved with moderation by a human. The intent is to add friction for knee-jerk low-quality comments, not solve for people who persistently, intentionally post low-quality comments after a warning.
I asked for a showdead feed to make it easier to train an LLM on for this purpose but got denied.
Not sure what you're referring to, but you don't need a showdead feed to train an LLM for this purpose. Only 2% of comments are dead, and the number of bad comments that aren't dead is certainly higher than 2%. That's the problem, in fact!
I have a compliant : sometimes there a proliferation of anti-scientific posts, in example I can mention those related to the "50 years nuclear battery", I remember particularly one from techradar.com that was especially misleading and anti-scientific and more similar to a PR campaign then scientific information, they was stating che you can power a smartphone or a drone with a betavoltaic battery (millionth of Ampere ). This is only an example, I noticed similar article , often related to green energy with the same anti-scientific cut and sometimes anti-scientific is a euphemism. Could nice to have a way to report them , even for occasional readers like me. Often the same articles have approval posts that IMHO are bot made. we live in times where scientific fraud amplified by the media is becoming a serious problem and I think everyone should do more to stop the phenomenon.
Trying to assess what's scientific vs. anti-scientific is outside the scope of what mods can do. I have my opinions just like you do, but hashing these things out is a community process, not a moderation issue. We could put our fingers on the scale, I suppose, but nothing good would come of that, so we don't.
Here's one from last week:
"Ring will no longer allow police to request users' doorbell camera footage" (npr.org) https://news.ycombinator.com/item?id=39138423
I posted an on-topic supporting quote to explain why this item was newsworthy and got one unhelpful one-word response and my comment got inexplicably flagged (not the commenter) https://news.ycombinator.com/item?id=39138481
How did that slip past detection? How do I get the abusive flag on my comment reversed? This behavior seems to have managed to push an important story off the frontpage quickly. (yes there was a badly-worded dupe headline, but that's a separate thing)
If I understand correctly, you have three concerns here: (1) the story was downranked off the front page; (2) your comment was flagged; (3) a comment that replied to you was not flagged. I'll try to respond to these in turn:
(1) the story was downranked off the front page because the topic had already been discussed a bunch—for example in these threads, two days earlier:
Amazon's Ring to stop letting police request doorbell video from users - https://news.ycombinator.com/item?id=39119387 - Jan 2024 (141 comments)
Ring steps back from sharing video with police – mostly - https://news.ycombinator.com/item?id=39120892 - Jan 2024 (15 comments)
Culling repetition from the front page is one of the most important things HN's systems need to do. Actually, it's probably the single most important thing. Certainly it's best if we can link to the previous discussions so people can know where to find them—but we can only do that some of the time. Users help out a ton by posting links to earlier threads. Ultimately we need better software support for dealing with this, but that's not done yet.
(2) Your comment https://news.ycombinator.com/item?id=39138481 was flagged by users. We can only guess why users flag things, but in this case I'm pretty sure I know why: comments that do nothing but quote from the article, or try to summarize the article, are considered too formulaic by readers here. If you want to say what you think is important about an article, that's fine, but please do it in your own words and share your own thinking. To simply paste a quote from the article is too superficial. On HN the convention is to assume that readers are smart enough to evaluate an article for themselves.
(3) The reply https://news.ycombinator.com/item?id=39138536, which only said "and?", was definitely an unsubstantive comment that deserved to be flagged (and killed) even more than yours did. The reason it escaped detection was simple, albeit unsatisfying: pure randomness. We don't come close to seeing everything that gets posted here—there's far too much. I've flagged it now.
How 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.
User 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.
I'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.
The 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).
It's good that this is in this thread, as I bet a ton of power users (I check HN multiple times a day for years but likely only a time or two have glossed over the FAQ), did not know FLAG could be used as a downvote tool. Interesting choice by PG, I agree with the previous comment, we have all come to know FLAG as a violation tool on most platforms. Now we know.
I'm surprised by this thread too.
I never flag anything because it's recorded on my profile, and I don't want stuff recorded on my profile that isn't useful to me. I only upvote submissions and comments that I intend to refer back to in the future. Upvotes are simply bookmarks to me, so my only tool for voting on the quality of conversation is downvotes. Which, apparently, I can't do for articles without spamming up my profile.
Actually I just checked my profile and saw several flags that must have appeared on a mis-click, just like how sometimes upvotes appear on a mis-click. Fortunately, unlike mis-clicked upvotes, you can still remove these.
Do you happen to remember if the misclicks were on mobile or not? I'm planning to add a confirmation screen to cut down on flags-by-misclick, but the current intention is to make it mobile-only.
I've ran into this a few times, not just with flagging but with hiding too. It would be really helpful to have a confirmation dialog and/or a banner on the screen after the action was taken that would let you undo it. To answer your question: I think most of mine were on mobile but it would be nice to be able to have it in all environments if possible.
Almost certainly they were on mobile, where the small font and use of touch screen to scroll makes mis-clicks much more likely. I'd be happy with a confirmation screen because I rarely or never intend to flag, but by the sounds of it there are a lot of liberal flaggers who could find the extra step annoying.
Not the original poster, but in my case it's always mobile.
Thank you for your tireless work. HN is a breath of fresh air compared with the rest of the internet thanks to it.
Tbh if you just upvote what you like and do not vote what you don't like it's almost the same thing.
The one exception is if some group organizes to upvote something that fits their agenda / business plan. But in this case it's generally something worth flagging and it gets flagged?
Why don’t you make the system transparent? This will save you a lot of effort answering questions.
"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&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 reasonably well for the bulk 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!
Envision an airline withholding safety records, a car manufacturer keeping crash test results private, a restaurant refusing to provide health inspection logs, or a government refusing to disclose details of its budget allocation — all claiming that transparency would only complicate matters and provide "more data for distrust". In each case, the flawed nature of your core argument becomes obviously evident.
I fully expect your mindset and behavior to never change (unless forced), but just wanted to point out that your argument against transparency is a cop-out and that you're on the wrong side of history here.
I think the fundamental difference is that an airline or government is working according to objective rules and regulations, while HN is not. HN is trying to build a community, and I think that communities need subjective rules rather than objective
I don't think you can reasonably compare the importance of transparency in your examples to that of editorial decisions in a private moderated community.
In the first set, the stakes are far higher, which is why the collection of objective data is legally mandated in the first place.
In the second set, you have only the subjective opinions of people who have an explicit goal to cultivate a specific variety of community. As members of that community, we select into the cultivation regime under which we participate. Not everyone will share the same preferences, and that's OK.
I have to admit, I laughed when I realized you are using a throwaway account, making this a strange work of performance art.
That's interesting! But I don't think the "flawed nature of my core argument" is obviously evident—and I don't think the community would consider that obvious either.
It could be fun to look into it together, but the fun stops at "I fully expect your mindset and behavior to never change". Why dance if someone wants to kick you in the shins?
While you argue against transparency, keep in mind that you are doing it in full public view.
People will game it. We don't need a transparent algorithm when we have transparent results, e.g. enable `showdead`, or the OP's project.
If you have nothing to hide, why not make all story and comment removal history publicly visible, like Wikipedia edits.
Wikipedia can and does vaporize edits.
I 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.
Just enable showdead if you want to see all of that. It's 99% botspam.
That 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.
That would create a bureaucratic nightmare for no significant gain.
Edit: see https://news.ycombinator.com/item?id=39234189 for a longer answer; and also krapp's comment at https://news.ycombinator.com/item?id=39232795, which makes a similar point.
HN 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'!
The url for this page is https://news.ycombinator.com/item?id=39230513 so the id is 39230513
I 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
Presumably its the id parameter in the URL?
Most likely in the URL, id=3923
The 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?
I assume you mean this one:
Avoid Async Rust at All Cost - 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!
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&que...
[2] 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&que...
[4] You Don't Have to Be a Jerk to Succeed - 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 - 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 - Jan 2024 (64 comments)
Google layoffs: Tech giant to cut down 30k jobs, says report - 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 - Nov 2023 (2 comments)
The NSA Invented Bitcoin? - https://news.ycombinator.com/item?id=37599194 - Sept 2023 (61 comments)
Leaving the Web3 cult - 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 - 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 - May 2023 (5 comments)
Is your husband/ boyfriend gay? LGBTQ - https://news.ycombinator.com/item?id=35734086 - April 2023 (0 comments)
dang, thanks for taking the time for such a thoughtful response. I didn't know about the policy regarding topics that have been on a lot lately, that makes sense. I've not been around as much lately and hadn't noticed that this topic was well-trodden.
By "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.
Of 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.
I don't necessarily want to dissect every little story, but this post was a funny edge case:
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=39186297
I don't really have a critique or solution here, I imagine false negatives are an inevitability. Just sharing.
We 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&que... that there had been a lot of submissions, and from 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 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, 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" :)
Ahh, 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!
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.
Or include the URL rather than just the HN ID so readers can follow the links.
yes! good point. Edit: I changed my GP comment to say "link" instead of "ID".
Thanks for replying with added context, didn't really mean to add more to your plate with this!
No 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)
I don't agree with the GP at all. Most seem normal for the front page or the intellectual curiosity standard (I mean, personally I'd like a much higher standard, but I'm basing it on what HN already has).
All from only one day:
* Ford's new 48-inch digital dashboard is a lot of Android for one car: https://www.theverge.com/2024/1/22/24045932/ford-android-scr...
* Secret Plan Against Germany (a very big story in Germany about a far-right planning meeting): https://correctiv.org/en/top-stories/2024/01/15/secret-plan-...
* Show HN: Vx.dev – GitHub-Powered AI for effortless development: https://vxdev.pages.dev/
* Open Source Doesn't Require Providing Builds: https://codeengineered.com/blog/2024/open-source-not-builds/
What these are is evidence of your parent comment's point that this isn't direct moderator action, rather a combination of algorithms and user flags.
Most likely, people flagged the Germany story because it has a sensational title and they likely aren't from Germany and so wouldn't have context to know whether it's overblown.
I'm confident that Vx.dev got flagged by a bunch of people because they're tired of LLM stories (as repeatedly attested in this thread).
Based on the ratio of comments to upvotes, I suspect the Open Source Builds and Ford discussions ran afoul of the overheated discussion detector. Usually when the ratio gets too lopsided the software automatically drops the post off the front page, because that's an indicator that a lot of people are arguing in the thread without actually reading or enjoying the article.
There ought to be a time-based flagging limit, so that people don't abuse the system. I've already raised this earlier.
If Company A makes a killer product announcement, rival Company B could simply get its employees to spam down votes on and flag that post. Company A gets less visibility, and dang won't be able to come on time to stop it.
This is an easily plausible hypothetical, which may already be happening.
Flagging requires high HN karma. You get that by being a positive member of the community. Most such people, if a company even has one, would find it against their personal ethics to do that. And dang can see the karma ratio and unflag any actually worthwhile announcements.
I think as people have become more and more aware that flag negatively weights items for rankings, and isn't just a "hey have the mods look at this rule breaking thing", more people have started using it as a downvote button. It was my understanding that HN originally didn't have a downvote feature to avoid the kind of issues that the flag usage is now causing.
Even the highest karma users can lose their flagging privileges, temporarily or perhaps even permanently, if they do it enough times within a time window or if abuse is detected. So from what I understand that issue should be taken care of.
I think you're probably generally correct, but "blaming the algorithm" sure smells to me like a whole lot of camouflage for censorship, which we ought to know by now has as much to do with 'quality' as it does 'shaping the narrative'
Generally speaking HN is a good site and a case study in successful community moderation, but you have to wonder 'who's watching the watchers' these days as the Overton window on free speech continues to be narrowed, almost entirely at the behest of big tech.
The simple solution would be to display a log of all removed/flagged/shadowbanned posts and comments, like Wikipedia does.
Preventing the site from being taken over by incessant meta debates is one of the moderation goals of the site.
https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...
(In many places there, obviously a lot of that is about Meta the company).
Periodic threads like this one are, I think, allowed as a sort of escape valve for pent up meta energy. Emph. on "periodic".
If you want a site that makes the opposite call here, Lobsters has a public mod log. You might like that system better!
Enable showdead in your profile if you want to see dead posts. You can't see deleted posts as the author deaded or asked HN to delete the post. See the HN FAQ [0].
[0] https://news.ycombinator.com/newsfaq.html
Does that mean stories about LLMs or by LLMs?
Serious question.
I am one of the (few? many?) people (devs) who haven't look into LLMs or even tried out ChatGPT yet :), except to make jokes about it here once in a while.
I think generally it works well- when there are actual major events like early COVID or Ukraine - HN managed to inform we way ahead of mass media with various interesting sources. But I’m happy to have a “news” thing pop up only a few times a year. You’re gonna have someone be mad about every instance when you moderate
Not sure why both submissions about work preferences were flagged:
https://news.ycombinator.com/item?id=39103328
https://news.ycombinator.com/item?id=39103483
Users flagged them. We can only guess why users flag things, but in this case it might have been the desire to avoid gender flamewar hell, which is mostly always the same and which HN has had more than enough of. Also, one of the submissions was paywalled (https://news.ycombinator.com/item?id=39104886), while the other was just the tweet of a graphic.
We sometimes turn flags off on such submissions, assuming that the article is substantive enough to have a chance at supporting a thoughtful discussion; and also assuming that the topic hasn't been discussed recently. But neither of those particular submissions was likely to be such a solid foundation.
It doesn't look like https://journals.sagepub.com/doi/10.1177/00169862231175831, the paper, has been submitted yet. That one might work, if you or someone wants to try submitting it.
Ok, I'm finally getting to this - sorry for taking so long! First let's find the actual HN submissions... here they are:
Ford's new 48-inch digital dashboard is a lot of Android for one car - https://news.ycombinator.com/item?id=39089599 - Jan 2024 (78 comments)
Secret Plan Against Germany - https://news.ycombinator.com/item?id=39092116 - Jan 2024 (5 comments)
Show HN: Vx.dev – GitHub-Powered AI for effortless development - https://news.ycombinator.com/item?id=39091819 - Jan 2024 (34 comments)
Open Source Doesn't Require Providing Builds - https://news.ycombinator.com/item?id=39094387 - Jan 2024 (68 comments)
Of those 4, the Ford one and the open-source builds one set off the flamewar detector (a.k.a. the overheated discussion detector); the Germany one was flagged; and the Show HN one got moderated down. Let's look at what happened in that order.
The Ford one setting off the flamewar/overheated detector is easy to understand: hatred for modern car UIs is one of the most popular topics on HN these days and always gets people going (me too! but never mind)...which no doubt is one reason why the media sites keep playing it up. We wouldn't turn the penalty off in such a case. The discussion might not have been a flamewar but it was nearly entirely generic - for example the top comment: https://news.ycombinator.com/item?id=39090622. Given how over-discussed this topic already is, I'd say this is a case of HN's software working as intended.
The open-source one setting off the flamewar/overheated detector is also unsurprising as open source stuff is also highly discussed and also gets people going. In this case I could make a case for turning off the penalty, but in the end would probably decide against it, because the article isn't very deep, the discussion is rather generic, HN has a surplus of such discussion already, and nothing here really clears the quality bar. But it's more of a borderline call; I can see how others could interpret it differently.
"Secret plan against Germany" was flagged by users. That's a political story with a baity title, so the default would be for it to get flagged. We sometimes turn flags off on such stories but I don't know that this one clears the bar. It's more current-events than deeply-interesting, the ideological material is inflammatory and nobody is going to approach it with curiosity. The thread was already showing clear signs of turning into a flamewar. Even then, we might still turn off the flags, but only if the story were intrinsically of great significance—the sort of thing it just wouldn't make sense not to discuss at all. I doubt this clears that bar.
The Show HN, we moderated down because "star for free trial" is not a valid thing to do in a Show HN and is something the community here would strongly oppose (see the top comment). Here's what I emailed the submitter: "We downweighted the post after getting complaints from users. 'Star repo for free trial' is way too much of a hard sales tactic for HN, and even more so for Show HN, which implies that users can try out the product (see https://news.ycombinator.com/showhn.html). Asking them to star your repo first may be an ok tactic in other communities, but in the HN context it comes across as manipulative and is not in your interest at all."
---
I guess the summary here is that this list is a mix of clear calls and borderline calls, but defensible ones. Anyone is free to disagree of course! No two readers, including mods, would ever make all the same calls. But if you do disagree, please keep two things in mind:
(1) You have to take each decision in larger context. A perfectly good story can be a bad fit for HN's front page if, for example, the story has already had a lot of discussion; and
(2) If we moderated cases like the above ones significantly differently, the consequence would be letting a lot more stories onto the front page that are significantly more repetitive and/or sensational than the median front page story is today. I doubt that most readers would want that. You can't think of this in terms of particular submissions or topics; there needs to be some principle according to which the decision would be made differently. Given HN's mandate, we're trying to optimize for intellectual curiosity. If there's a way to do that better, I'd certainly like to know what it is; but given the mandate, that's the only kind of change it would make sense to implement.
dang - thanks for taking the time to respond in detail. You really go above and beyond. I imagine this whole discussion landing like a concrete block on your plate (but hey, maybe you dig this part of the job).
I have/had no objection to the moderation on these posts. In fact, if I were monarch of HN and the Internet, I'd want an order of magnitude higher standard for the quality of posts, comments, and conduct. I want to spend my time and on the actual very best intellectual content and discussion possible - it would probably be mostly the very best books and papers from journals if I had my way. (Not that I think HN should serve my personal preference, I'm just demonstrating that I am far away from criticizing the moderation.)
My GP comment and my other one that you responded to [0] were trying to recenter at least part of the discusson on a factual basis, which I find much more interesting than the (completely unintersting) conspiracy theory aspect. That is, if we explore it factually, objectively, intelligently, how does it work? how does it work out? For example, I imagine there are some interesting emergent properties which would tell us about the HN population, emergent properties of algorithms, and the interaction of both.
[0] https://news.ycombinator.com/item?id=39231055
The second one is both sensationalist clickbait[1] and politics. It was rightly removed:
https://news.ycombinator.com/newsguidelines.html
It's not as if the internet is lacking in places where this can be discussed freely.
[1]: As in you have to click the link to see what it is about, and to decide if it is interesting or relevant to read.
The second story is evidence of a new phenomenon: The far right political movements thinking about an anti-constitutional policy, a new step on the ladder of escalation.
There's a reason it's a big deal in German politics and already had some fallout (and thankfully multiple dozens of counter-demonstration of ten of thousands of people all over Germany.)
The things you see on HN are not purely decided by the community. Mods can and do "freeze" the vote count on comments and posts, and do other non-obvious things too. You will notice the effect after participating for a while.
Exactly, the front page is heavily moderated. Almost every day you'll see posts with 50+ upvotes falling of the front page within an hour or two when some article about LISP with < 10 upvotes will remain here for a whole day.
It's disingenuous to blame it on the users when there are clearly other "forces" at play here.
The "force" is actually one or two people. It's hard to prove and impossible to change. No one will believe you, either.
Could you make your accusation more clearly? Are you saying it's 'dang' and 'pg'? One or two regular users abusing the flagging system? Or a couple dark and shadowy figures who have no public presence?
I don't mean to make accusations or invent "shadowy figures". HN has a very small number of moderators and their actions are not transparent, that's all.
Thanks for clarifying. I think part of my confusion was that HN only has one moderator at this point. Also, I'd probably say "not always obvious" rather than "not transparent". While there is no public record of moderation, at least for me Dan has been excellent about answering questions when asked.
Yes. I will use the words you want me to use, and not my own words. Thanks for helping me out.
I think you've misinterpreted my tone. I was not trying to tell you how to speak, but rather how I view the issue. You are welcome to share your own view.
If it works..
There are a billion forums with less stringent moderation. Moderation is a very large part that makes HN good and not so game-able like most sites
I’m sure the HN codebase has some secret creed to make lisp more popular
The code is written in Lisp, but it doesn't know that and has no way (edit: that I know of) to expand its empire.
Yes, HN is a moderated/curated site and always has been. Here's 10 years' worth of me explaining that: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...
What people maybe don't realize is how many constraints there are on HN's system. There aren't many degrees of freedom for us to change things that wouldn't lead to a massively different site, and most of those outcomes would be worse, because most of them would be closer to internet default.
It's easy imagine "HN, but without the things that I personally find annoying". But try to generalize that for a moment and the problem quickly becomes intractable.
We don't freeze vote counts. What made you think that we did?
Comments on frontpage posts that go up quickly but then suddenly don't receive any votes in any direction makes me think you do freeze vote counts.
We definitely don't. But I'd love to see any links to posts where you've seen that—or if you see it in the future. It's an unusual case that I've never heard of before!
The reason I say we definitely don't is that we'd have to write code to do that, and I'd remember writing such code.
Thanks dang, I appreciate your efforts. I have no reason to doubt your word, and I may have imagined a pattern. I apologize for the accusation.
YMMV. I don't want to see Altman's fearmongering and hyperbolic statements.
At this point he's indistinguishable from a bitcoin advocate or a tv preacher.
It's dubious that HN mods think that way of Altman though.
s/mods/users? everyone can flag stories.
It's not flags (or not sufficient to remove the story):
https://news.ycombinator.com/item?id=39231055
Flags are sufficient. I just posted a comment on the comment you linked to: I have many times been the person who pressed "flag" on a story and then watched it immediately disappear.
I think there's some threshold of flags to upvotes and possibly some other metrics that determines whether a story vanishes, but flags can absolutely tip the scales.
I like Sam, but "$celebrity says $thing about $common-topic" is almost never a good basis for a frontpage thread on HN.
It's vital to HN that user flags and/or software like the flamewar detector clear most such submissions off the front page. They tend to attract a lot of upvotes because that's what sensational (and especially indignant-sensational) stories do. Without countervailing mechanisms, HN would be completely taken over by those stories.
His statement wasn't even hyperbolic or fearmongering.....?
He just extrapolated based on current amounts of compute and estimated a possible model size that could be equivalent to AGI (based on current architecture).
Training a model of that size would require too much electricity.
That was his point.
The Altman story was likely a dupe (or triplicate)
Why not redirect to the original story?
Dupes generally drop off the front page, whether or not someone links up the previous stories in the thread. The whole point is not to let the duplicate story crowd out other stories on the front page. Redirecting would defeat the purpose.
Is that possible?
moderators are not omnipresent, and some times the users are faster to react than the mods.
We do redirect to earlier posts that had the exact same URL. But most dupes, in the sense of repeated posts about the same story, don't have the exact same URL. What do you do then? That's a hard problem. It would be great to have an automated solution to that but I don't know of one.
Two out of three currently aren't removed. There's no moderator comment on the third, but a fair number of upvotes and user comments; I think it was flagged by users.
Open Source Doesn't Require Providing Builds
https://news.ycombinator.com/item?id=39094387
Sam Altman Says AI Using Too Much Energy Will Require Breakthrough Energy Source
https://news.ycombinator.com/item?id=39095738
Avoid Async Rust at All Cost (flagged)
https://news.ycombinator.com/item?id=39102078
There's a difference between removed and removed from the front page.
IIRC: Mods can downrank a post so that it doesn't change anything for users, aside from the fact it won't be on the front page.
That's a big change?
How can you tell? Those are from a week and a half ago. The OP's definition of 'removed' is (if I understand correctly) 'dropped from the top-30 to below the top-90 in 1 minute'.
HN is a leftist echo chamber, so “flagged by users” is still a relevant and interesting metric here (that I think would also prove my point).
Sam Altman led invests in a nuclear fusion company, Helion. Guessing the potential conflict of interest is why the 2nd article drew vote controversy.
https://www.helionenergy.com/articles/announcing-500-million...
This is the kind of explanation that makes sense when the association happens to come to mind—in this case, something like: HN -> YC -> Sam -> Helios -> nuclear -> obvious conflict of interest -> QED. But such chains of associations rarely have anything to do with what happened to a story on HN. The explanation is almost certainly much simpler.
In the case of https://news.ycombinator.com/item?id=39095738, it just set off the flamewar detector, a,k.a. the overheated discussion detector. We sometimes turn that penalty off, but in a case like this we wouldn't do that because "$Celebrity says $thing about $common-subject" is almost never a substantial story. It's essential to HN to clear such stories off the front page in order to make room for more interesting, less sensational things. If we didn't, the front page would consist of little else.
Possibly dups too.
The last story is so full of outdated and misinformation that I tried to find out whether it was written a few years ago (though it would have still been full of misinformation back then).
I suspect that it has been flagged for that reason by multiple people.
I witnessed a recent front page link silently get changed to point to a parody video, then silently changed back later, with the top comment that remarked on the change silently removed.
That told me all I needed to know about the moderation of this site.
Thankfully someone captured a screenshot: https://merveilles.town/@cancel/111834048502040552
Dang explained it was a mod error: https://news.ycombinator.com/item?id=39182625, which links to https://news.ycombinator.com/item?id=39170137
huppeldepup's comment in the screenshot is collapsed on p2 of the comments (after it was no longer relevant) https://news.ycombinator.com/item?id=39157010&p=2, and is also accessible as the parent of https://news.ycombinator.com/item?id=39170137.
What did you think he was going to say? Explain that it was in fact a big HN conspiracy?
I mean yeah it probably was just a mistake but what do you expect somebody to say?
I expected a matter-of-fact explanation of a simple error, and a comment thread that was collapsed - exactly what I found. reductum implied there wasn't an explanation and that the complaining comment thread had been deleted without comment, both of which were hard to believe, so I went looking.
You just need to move your game theory to a different level. The expected value of lying about such things is super negative and the expected value of telling the truth is super positive.
I'm sure there's a model in which lying some of the time but not too often has marginally higher expected value, but it's also going to have significantly higher risk and that's not worth it, plus you have to be disciplined enough to actually apply such a strategy. One slip and you're dead! I'm too lazy for that.
In that case you drew a general conclusion from a freak accident so rare that I doubt it had happened in the 17 years this site has been around. (Edit: 17 years this month in fact! https://web.archive.org/web/20070221033032/http://news.ycomb...)
If what you require from an internet forum is that the moderators under no circumstances will ever commit a copy/paste error, HN is definitely below your standards.
Edit: the mods would like to share that they weren't drunk when they made that mistake, just rushed and watching a rather gripping tennis final.
That prompted me to check other dates in the archive: apparently the "Startup News" title lasted for around six months before changing to "Hacker News". I was pretty sure the change was before I made my account, but I didn't realize the "Startup News" period had been so short.
pg got bored of startup news and switched it in August of that year:
https://news.ycombinator.com/hackernews.html
Edit: here's the last copy of Startup News that archive.org has—from 2007-07-13:
https://web.archive.org/web/20070713212949/http://news.ycomb...
and here's the first copy of Hacker News they have, from 2007-08-30:
https://web.archive.org/web/20070830111558/http://news.ycomb...
They missed an entire 6 weeks there, but bless them for having anything at all—who among us preserves our own history?
Garry Tan seems to benefit from this system as well. Nothing sensationalist about tracking his awful behavior.
We haven't touched those stories except reduce the penalties on them (user flags mostly) and moderate them less than we normally would (per https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...). I put one back on the front page last night despite this contradicting every principle HN stands for—every other principle, that is, than the first one, which is that we moderate HN less, not more, when YC or a YC startup is part of a story.
I posted detailed explanations in those other threads:
https://news.ycombinator.com/item?id=39224560
https://news.ycombinator.com/item?id=39210947
https://news.ycombinator.com/item?id=39172045
If you (or anyone) read those explanations and still have a question that I haven't answered there, I'd like to know what it is. These practices have been in place for many years and haven't changed.
@dang Thank you for the info.
One questions I do have–I would guess posts critical of HN/YC are going to get a log of flags and have not the best discussion. This has a side affect of biasing the home page to not have posts critical of HN/YC. Do you see this as a problem?
You can take this with a grain of salt as I'm obviously not the most neutral observer, but from everything I've seen (which at least is a lot!), yes they get a lot of flags, but they get even more upvotes. It's hard to say which side wins out in the tug-of-war. The tendency towards negativity that jsnell's comment describes is very real, and it's on the upvote side in these cases.
Most probably the tug of war goes one way some of the time and the other way the rest of the time. The funny thing is that as mods, we have to have a regulating influence either way. What I mean is that if a rage story hits the top of the front page, we'll downweight it (though not necessarily all the way off the front page); but if a rage story about YC gets too many flags, we'll reduce those or remove them altogether. The recent shitfest is a good example; let me dig up some links for you... Edit: oh wait, I already mentioned those links in the GP. Sorry, I'm getting a bit tired here!
Did I answer your question?
@dang You did–thank you. I hope my question didn't come across as accusatory. This is a hard problem and, unfortunately for you, many of us enjoy discussion of difficult problems. What many of us may not see is you having to have the _same_ conversation over and over. Thanks again for your work. I don't envy your position.
Oh you're welcome, thanks for the kind reply. One thing I've learned from this thread is how much misunderstanding there is around follow-up or duplicate articles that get moderated because they're repetitive, not because they're off-topic in themselves.
The home page already has a massive bias in favor for pretty much any kind of negativity, but doubly so for anything involving a tech company. It doesn't matter whether the stories are untrue, unverified, repetitive, etc, they'll still get voted up, and the comment threads will half full of low quality complaints repeated from past discussion, often only tangentially related to the submission.
And it creates a very visible feedback loop, as users start to think that this is what HN is supposed to be. They're probably the biggest quality problem of HN.
dang has been doing a fantastic job for years now. How big is his team? What kind of tools are they using? Would love to read a writeup sometime, but I guess there are good reasons to keep this secret.
https://www.newyorker.com/news/letter-from-silicon-valley/th...
Tldr the answer is “2”. Not sure how posting a link where this info is buried is helpful.
The answer to OP’s first question, but there was a second one:
Then downvote it, that's what the button is for! The other commenter said they were interested in a write up with more information than that one question. But hey, can't please everyone.
sctb stopped working on HN in fall 2019, alas!
https://www.nasa.gov/solar-system/asteroids/nasa-system-pred...
Really? A NASA report, on the official .gov site? Maybe the comments were horrible but that seems right in the middle of what HN is interested in.
You're talking about this submission:
NASA System Predicts Impact of a Small Asteroid over Germany - https://news.ycombinator.com/item?id=39126705 - Jan 2024 (18 comments)
It was downweighted because it was a dupe (or quasidupe) of this:
Scientists discover near-Earth asteroid hours before it exploded over Berlin - https://news.ycombinator.com/item?id=39103412 - Jan 2024 (46 comments)
That's the system functioning as intended. We work hard to try to prevent repetition from taking over the site, because repetition is the enemy of curiosity (https://hn.algolia.com/?dateRange=all&page=0&prefix=false&so...).
One thing I've learned today, after 11 hours of posting in this thread, is that it's easy to look at an article in isolation and say "Really? That got moderated?" - when in fact if you know the larger context there's nearly always a straightforward explanation.
One can certainly argue that 86 points and 46 comments is too low a threshold to treat the repost as a dupe, but that's a different question, no?
The effort is appreciated by some if not most.
It wasn't 11 hours straight by any means. But thanks! It's nice of you to say that.
When I get tired I start to complain. It's a bad habit.
Props to the mods for keeping the post quality high.
However, I do see a few decent posts in this list that probably warrant a second chance.
Happy to look at specific links if you want to mention any!
The moderators are mainly the users. Flags are what kills a story quickly
You're right, but I'd like to add that we do turn off flags sometimes when we think a story (a) has a good (if not high) chance at a substantive discussion and (b) hasn't had much discussion previously. If anyone notices such a case, they're welcome to email us at hn@ycombinator.com and we'll take a look.
Agree, and to be clear, that's why I upvoted this submission -- it really is an endorsement of the algorithm and moderation we see here. I know the person who wrote the article did it from a place of skepticism, but it functions as a nice gold-star transparency report.
plural ?
Another way to look at this is that the mods have the same biases you do. Depending on how you’re feeling on a given day, you could call that an echo chamber.
Yeah this list seems to be pretty low quality stuff. There's a couple economic/political links that I think are interesting but I can totally see why they would be removed as off-topic or likely to produce a flamewar.
It's pretty clear to me that any online forum needs good moderation to be healthy long term. HN has been good about this with a strong community providing upvotes/downvotes and a moderation team that seems pretty light handed but not afraid to say no when necessary. Please keep doing what you're doing.
It really is impressive how HN has been such a quality community for so long. I can’t think of any of many other online communities that I have been using for 10+ years. So definitely much gratitude to the mods from me for the work they do.