A post titled "How to Passive-Aggressively Shame People Who Use LLMs Selfishly" appeared on Hacker News and collected 30 points with 18 comments.
The discussion centers on etiquette around LLM usage in shared spaces such as code reviews, documentation, and public writing.
What the Post Describes
The core idea outlines indirect methods to highlight when someone relies on LLMs without adding original value. Examples include quoting generated text back with minor edits highlighted or asking for the original human-written version in follow-up threads.
These tactics aim to enforce norms without direct confrontation.
Community Numbers and Reactions
The thread received 30 upvotes and 18 comments within the first day. Participants noted patterns of LLM output in technical posts, with several comments citing repeated phrasing or generic structures as red flags.
Early replies focused on detection signals rather than the shaming methods themselves.
How to Apply Similar Signals
Developers can flag potential LLM content by requesting specific clarifications on edge cases mentioned in the text. Another step involves comparing the post against common model output styles using simple string searches for overused transitions.
These checks require no extra tools beyond a browser.
Pros and Cons
- Pros: Raises awareness of attribution without escalating to bans.
- Pros: Works in public forums where direct calls can be moderated.
- Cons: Risks mislabeling non-native English writers or concise human drafts.
- Cons: May reduce overall participation if users fear indirect criticism.
Alternatives and Comparisons
Direct private messages offer one path. Public guidelines in repository README files provide another. A third option is automated detection scripts shared openly.
| Approach | Visibility | Risk Level | Setup Time |
|---|---|---|---|
| Indirect comments | High | Medium | Low |
| Private DMs | Low | Low | Low |
| Repo guidelines | Medium | Low | Medium |
| Detection scripts | High | High | High |
Who Should Engage
Teams maintaining public documentation or code review standards benefit from clear norms. Individual contributors working in high-volume forums may skip these tactics if their focus is speed over attribution.
Researchers tracking LLM impact on writing quality can treat the thread as one data point among broader studies.
Verdict on Effectiveness
The discussion shows limited consensus on enforcement methods, with most comments favoring transparency requirements over social pressure.
Bottom line: Community norms around LLM disclosure remain informal and depend on platform culture rather than standardized rules.
The thread illustrates how early adoption friction appears first in comment sections before any tooling catches up.
Top comments (0)