news.ycombinator.com via Hacker News

Hacker News Debates User-Facing Flag for AI-Generated Articles

TL;DR

  • An Ask HN post proposing a user-visible flag for AI-generated articles drew 430 points and 222 comments, an unusual level of amplification for a moderation meta-thread.
  • Moderator dang confirmed HN already prohibits AI-generated text in submissions and comments, saying 'We don't allow genai text on HN itself.'
  • Instead of a visible AI tag, dang floated adding a 'please give a reason why you flagged this post' step, with AI-generated as one selectable option.

A meta-thread about moderation is not usually the thing that dominates the front page of Hacker News, but an Ask HN post arguing the site should add a user-visible flag for AI-generated articles pulled 430 points and 222 comments. The submitter, levkk, asked why regular voting was not enough, and whether the site should evolve its fundamentals in response to generative AI.

The most interesting response came from moderator dang, who confirmed the site already prohibits AI-generated text in submissions and comments, writing 'We don't allow genai text on HN itself.' Enforcement, he acknowledged, is the harder part. Rather than adding a visible AI tag, dang floated a change to the flagging workflow itself, a 'please give a reason why you flagged this post' step, with 'AI-generated' as one of the selectable options. He described readers developing 'allergic sensitivities to language that sounds like an LLM produced it,' and pointed at an emerging 'class distinction between writing...that use genai vs. writing that does not' inside the community.

The pain point the thread keeps circling is a comment about engagement itself, that 'it's impossible to engage deeper with the material because the author doesn't really exist.' If the byline is a thin wrapper around a model, threaded discussion falls apart, because there is no author to ask a follow-up question.

The honest caveat is one the thread raises itself. False positives are the obvious risk. Non-native English writing can trip the same instinct that catches LLM prose, and some commenters defended limited AI use as no different from a spellcheck. A structured flag-reason list gives moderators a signal, but not one that is safe to auto-action on. What the reporting does not resolve is whether HN would ever publish stats from those reasons, whether the same rule applies to comments as to submissions, or how heavily an AI-generated flag would weigh against ranking given dang framed the request as labeling rather than de-ranking.

The forward-looking piece is who benefits if this ships. Every editorial channel where humans read for insight is running the same experiment right now, and a high-signal community like HN converging on structured flag-reasons rather than visible AI tags is the kind of pattern other platforms tend to copy.