Giving "AI slop" as feedback says as much about the commenter as the creator
Written 13 July 2026 Tags ai work Using "AI slop" as feedback tells as much about the commenter as the creator. The label can mean anything, gives the creator almost nothing to act on, and by its own definition reads a lot like human slop. A post I made recently saying "AI slop is a reflection on the human, not the AI" hit a nerve.
- ▪Written 13 July 2026 Tags ai work Using "AI slop" as feedback tells as much about the commenter as the creator.
- ▪The label can mean anything, gives the creator almost nothing to act on, and by its own definition reads a lot like human slop.
- ▪A post I made recently saying "AI slop is a reflection on the human, not the AI" hit a nerve.
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,271 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | the truth as I see it now |
| Canonical URL | https://thetruthasiseeitnow.com/using-ai-slop-as-feedback-tells-as-much-about-the-commenter-as-the-creator/ |
| Publication time | Mon, 13 Jul 2026 06:06:13 +0000 |
| Retrieval time | 2026-07-13T06:15:32.498Z |
| Last seen | 2026-07-13T06:15:32.498Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | dUUs-piA1BFP |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Written 13 July 2026 Tags ai work Using "AI slop" as feedback tells as much about the commenter as the creator. The label can mean anything, gives the creator almost nothing to act on, and by its own definition reads a lot like human slop. What matters is what you do with it. A post I made recently saying "AI slop is a reflection on the human, not the AI" hit a nerve. There was both agreement and disagreement at the same time. Rightfully so: it was a one-sided piece. Here is the other side. Using "AI slop" as feedback tells as much about the person making the comment as it does about the person being reviewed. Start with what the term even means. When I read "AI slop" under someone's work, I visualise a variety of different things. I hear: this post was AI-generated.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at the truth as I see it now.