logoalt Hacker News

dangtoday at 2:30 AM18 repliesview on HN

We don't allow genai text on HN itself - see https://news.ycombinator.com/newsguidelines.html#generated and https://news.ycombinator.com/item?id=47340079. How to enforce it is a separate question, of course, but the rule exists.

We don't have a similar rule yet about article content but my sense is that the community mostly doesn't want to read it—or, to put it more conservatively, discounts it. This is why we see so many "just show me the prompt" responses, along with others like this: https://news.ycombinator.com/genai-pushback. I built that list so I have something to send to users who email about why their genai articles got flagged.

It's a fascinating arms race right now: the AIs are training on the humans but the human hivemind is also training on the AIs. Readers are developing allergic sensitivities to language that sounds like an LLM produced it. The AIs will adapt to this, but the humans will adapt in turn. Where it ends up is anyone's guess. I have an optimistic view, but I've already been wrong about this so many times that I have low confidence in it.

The current picture is that there is an emerging class distinction between writing (and writers) that use genai vs. writing that does not. As soon as the "this sounds like an LLM" allergy kicks in, the writing instantly gets relegated to a low-status bucket in the reader's mind. That doesn't mean it won't still get looked at - but it is now under a stigma.

(I was rather pleased with the originality of this until I remembered pg had come up with "writes and write-nots" in https://paulgraham.com/writes.html. Oh well, it's the point that matters.)

This has the happy flipside that anyone who would like readers to classify their article as high-status rather than low-status can apply the judo move of simply writing it themselves.

Now I need to add the disclaimer that none of this is a dismissal of LLM technology per se. We rely on it heavily, and there's no question that it's useful. The question is how to use it (pg again: https://x.com/paulg/status/2058871512451412457) and whether one should use it on writing that one publishes to other humans.

To turn to OP's questions:

> Should HN add the ability to flag articles as AI-generated? [...] it could just show up as an indicator

Flagging-as-just-an-indicator would be tagging, which we've always resisted adding to HN, but I wouldn't rule it out.

What I do think we'll (finally) add is a "please give a reason why you flagged this post" step, and "because I think it's genai" will be one choice among several (spam, offtopic, mean, etc.)

> Why is the regular voting system not enough?

The regular voting system is never enough. https://hn.algolia.com/?dateRange=all&page=0&prefix=false&so...

> Should HN change in response to the gen AI era?

To this I am tempted to reply with https://news.ycombinator.com/item?id=48887149 in an homage to https://news.ycombinator.com/item?id=3742902.


Replies

grayclhntoday at 5:52 AM

I think classifying it as an allergy or a status thing is a little too glib. I’ve read and reviewed, conservatively, hundreds of AI generated documents for work, and “written”/commissioned a bunch too. My biggest issue is that it’s impossible to engage with and give feedback on an AI written document, because it’s impossible to know whether misconceptions or gaps are because the author doesn’t understand the material deeply enough or the author does but the AI doesn’t and the author’s not proofreading carefully enough. Or if a surprising idea is raised — is it the authors insight, can they elaborate on it, where did it come from, etc?

Hackernews isn’t work, obviously, but “it’s impossible to engage deeper with the material because the author doesn’t really exist” is sort of a problem for a discussion site. If the human coauthor puts in enough work, they can make sure the doc really reflects their views and their understanding, but in my experience that’s much less common.

show 2 replies
bhaneytoday at 4:22 AM

> What I do think we'll (finally) add is a "please give a reason why you flagged this post" step, and "because I think it's genai" will be one choice among several

Does that mean that an article being AI-generated is a flaggable offense? Should we be flagging suspected AI-generated articles already, or should we wait for the flagging system to support reasons first?

show 1 reply
avaertoday at 2:44 AM

I hope HN doesn't get into moderating the politics of articles.

I can see a grim future (present?) where "AI generated" turns into a slur, warranted or otherwise, in a world where the difference between human trained to talk like an AI and AI masquerading as human becomes increasingly difficult to discern, and some hidden cabal passes judgement.

That is wholly different from taking a stance on HN being a place for humans to comment on articles.

show 8 replies
abnercoimbretoday at 4:59 AM

> This has the happy flipside that anyone who would like readers to classify their article as high-status rather than low-status can apply the judo move of simply writing it themselves.

I really really hope more people take up pen and paper! My last blog post [0] came with proof-of-work attached.

[0] https://abner.page/post/are-we-harold-bloom/

show 1 reply
bigcityslidertoday at 4:38 AM

If AI-generated comments are disallowed, why are AI-generated articles allowed? Seems like they have the same issues.

show 2 replies
brudgerstoday at 4:56 AM

What I do think we'll (finally) add is a "please give a reason why you flagged this post" step

Do you believe adding friction to flagging will reduce the quantity of low quality articles?

Or is the flagging of high quality articles a bigger and more pressing problem?

Or is the problem simply too-many-damn-flags?

Just curious.

show 1 reply
clickety_clacktoday at 3:32 AM

The tricky thing about tags is that we get a tag for genai this year, what about next year’s thing and the year after that? We’d end up with a list of tags attached haphazardly all over the place. Flagging with a box to add a reason sounds like an excellent idea.

show 1 reply
aabhaytoday at 3:12 AM

Community generated tags seems like the obvious solution to all of this. You could easily give a setting to turn them off, breaks no existing systems, and allows for a broad emergent taxonomy. Only surface tags above X community upvotes except to superusers who are allowed to propose tags.

But then again, there’s always reddit :)

show 1 reply
1bpptoday at 5:12 AM

I would love to see a 'flag as AI' coupled with a profile setting to hide posts that have had a certain number of AI flags. Allow people who don't want to see likely AI content to filter it silently.

dcowtoday at 5:47 AM

My only thought is that "good" genai authors/articles will easily get through the filter while "generic" ones will fail. So the outcome won't be all genai articles getting flagged (unless people self-report), just the low quality ones. I'm guessing that's okay and I'm one of those people who discounts genai writing the second I read one of the tells, so the flag would save me time.

Ultimately though this is the same debate as "should we allow genai code in codebases". High quality code lands naturally while slop is slop. Not much value in banning AI outright--the desire is predominantly to ban the slop.

Maybe the tag should be [slop] rather than [genai]...

show 1 reply
cr125ridertoday at 3:43 AM

Great response. Thanks for weighing in and all the moderation you do!

ryukopostingtoday at 5:49 AM

> This is why we see so many "just show me the prompt" responses, along with others like this

Many are quite a bit more subtle, like this: https://news.ycombinator.com/item?id=48844062

The more subversive undercurrent is interesting to me. People intentionally fucking with someone's bot, burning tokens for the lulz.

show 1 reply
slgtoday at 5:35 AM

>This is why we see so many "just show me the prompt" responses, along with others like this: https://news.ycombinator.com/genai-pushback.

This is totally tangential to your point, but what is that page? It's not your usual link to an algolia search. Is this already part of some sort of manual tagging system? Clicking on the first one, these comments don't seem to be moderated. Are you using these complaints to help detect AI generated content? I think the existence of that page just leaves me confused on whether you actually want people to comment like this or not.

show 2 replies
152334Htoday at 3:55 AM

lots of things happening in this post

1st: the presumption that AI generated text is actually unsuccessful, rather than proliferating broadly unchallenged today

2nd: the disposition that negative attitudes towards AI text are unjustified discrirmination, rather than working as a strong latent predictor of low-effort content

3rd: the assumption that human writing is reliably doled benefits, rather than some poor proxy of it (winning the social contest for claiming authenticity)

Operationally, only a very small minority of humans actually successfully identify AI generated text at rates ≥ Pangram. People discriminate against the label of "AI", but mostly fail to vote accurately. It's not uncommon to see bots abusing this gap for their own success -- accusing humans, sympathizing with generated profiles... FUD environment where people routinely get away with dismissing true accusations.

For someone who is mediocre at detection, this would structurally feel like an unhinged, unjustified bias: look at all these good posts, these honest people, getting undermined by discrimination...

show 1 reply
tptacektoday at 4:15 AM

A fixed dropdown list of flag reasons would be a very good change, I think, because it would somewhat counteract strategic flagging of stories as a downvote. I think you'd want to keep the list pretty tight, because it seems like a huge source of meta drama.

show 1 reply
ludicrousdisplatoday at 5:52 AM

I don't rely on LLMs and I don't find them useful, hence I don't use LLMs and everything about them deserves to be questioned.

show 1 reply
bakugotoday at 4:13 AM

> The AIs will adapt to this

I don't think this is true, at least not right now, and in a way I'm actually thankful for it.

The frantic rush to chase the only potentially profitable use case for LLMs found so far (writing code) and the resulting focus on coding RLHF means models are actively becoming worse at sounding like humans.

This is my favorite example, and it's already relatively outdated: https://progress.openai.com/?prompt=10

jorvitoday at 2:46 AM

The times I've pointed point out pretty blatant AI comments, I get nuked with downvotes. So often that I've stopped pointing them out.

Before you say I'm just falsely calling them out, it's typical ChatGPT style of either very amicable or Nobel Laureate tone, lots of formatting, with a couple of paragraphs and then a clever one-line punchline at the end. If you look at those commenters their history, it's all like that. Either generated or assisted. For older accounts you can see the steep increase of it around 2025ish.

Seems like the HN crowd absolutely adores AI comments and the rule banning them is (sadly) unnecessary. Or at least not what 'the people' want.

show 3 replies