HN
Today

AI;DR (AI; Didn't Read)

A new viral acronym, "AI;DR (AI; Didn't Read)," proposes a decisive stance against unedited AI-generated content, advocating for a policy of ignoring anything that lacks human review and effort. This sentiment resonates deeply with many on Hacker News who are increasingly frustrated by the proliferation of verbose, nuanced-free AI "slop" in professional and social communications. The discussion highlights a growing tension between AI's potential for productivity and its impact on communication quality, authenticity, and intellectual honesty.

500
Score
310
Comments
#4
Highest Rank
16h
on Front Page
First Seen
Aug 17, 8:00 PM
Last Seen
Aug 18, 11:00 AM
Rank Over Time
648811129111418161418222629

The Lowdown

The article introduces "AI;DR," a concept mirroring "TL;DR" but applied specifically to AI-generated text. The author, Rick Manelius, expresses a strong personal frustration with receiving unedited AI output, noting a physical aversion to what he terms "AI slop." While acknowledging that AI is an integral part of many processes in late 2026, he draws a line when it comes to communication intended for humans.

  • The Problem: The core issue is the intellectual laziness perceived when someone sends unfiltered AI content. If the sender can't be bothered to review and edit, the recipient shouldn't bother reading.
  • Distinguishing Use Cases: Manelius differentiates between acceptable 100% AI-generated content (like customer support) and unacceptable uses, particularly in peer-to-peer communication like Slack or personal newsletters.
  • Loss of Authenticity: He argues that unedited AI prose, with its characteristic "AI-isms," undermines the personal pride and genuine voice that should accompany one's name.
  • Call to Action: The author urges readers to adopt the "AI;DR" policy themselves, encouraging a cultural shift where human effort and thoughtful editing are once again valued in digital communication.

In essence, the piece argues that the sheer volume of AI-generated content necessitates a new filter for discerning valuable, human-curated information from thoughtless, machine-produced filler.

The Gossip

Slop's Sour Stench

Many commenters echo the author's frustration with the inundation of AI-generated "slop." They lament the verbosity, lack of nuance, over-confidence, and general fakery of unedited AI text, particularly in technical contexts where precision and deep understanding are paramount. Anecdotes abound of AI content making big claims without addressing core technical challenges, or of colleagues submitting AI-heavy documentation and code comments that obscure rather than clarify, leading to post-readability codebases.

Prompt Power and Transparency

A recurring suggestion is that instead of sharing raw AI output, users should share the prompt they used to generate it. This highlights a desire for transparency and reproducibility, allowing the recipient to understand the sender's intent and even re-run or modify the prompt themselves. Commenters argue that the prompt often contains more genuine human intent and actionable information than the verbose, generalized AI response. Some even propose technical solutions like a "right-click -> view prompt" feature.

Detecting Deception and AI Tells

The discussion delves into the challenges and tells of identifying AI-generated text. While some point to specific stylistic patterns common in models like Claude (e.g., excessive em-dashes, smug tone, boilerplate phrases), others express concern about being falsely accused of using AI when their human-written content coincidentally shares certain characteristics. There's an underlying anxiety about what happens when "good writing looks like AI" and the erosion of trust in digital communication.

Workplace Woes and AI Overload

Many users share experiences of AI 'slop' infiltrating their professional environments, from colleagues posting unedited AI output in Slack and PRs to managers using AI for poorly defined assignments. This raises questions about how to address the issue politely and effectively, with some resorting to strict code review policies (e.g., character limits for PR comments) or even seeing colleagues fired for relying solely on AI to the point of incompetence. The consensus is that AI, if unchecked, can significantly degrade team communication and code quality.

The Effort-Value Equation

Commenters debate the evolving relationship between human effort, perceived value, and AI generation. Some argue that AI devalues human expertise and signals intellectual laziness, leading to content that isn't worth a reader's time. Others contend that if AI can produce valuable or insightful content, the 'who' or 'what' behind it is secondary to its utility. There's a concern that the ease of generating text with AI is eroding the quality of online discourse, replacing genuine insight with volume and boilerplate prose.