Linus Torvalds on the continued flood of AI bug reports
Linus Torvalds discusses the ongoing issue of AI-generated bug reports affecting website functionality. The article highlights the implementation of Anubis, a system designed to mitigate aggressive web scraping by AI companies. Anubis employs a Proof-of-Work scheme to make scraping less efficient and aims to improve methods for identifying automated browsers.
- ▪Anubis is designed to protect websites from aggressive AI scraping.
- ▪The system uses a Proof-of-Work scheme similar to Hashcash to deter scrapers.
- ▪Torvalds emphasizes the need for better identification of headless browsers.
9 outlets in our directory ran this story, first to last over 27 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
- ▪ Linus Torvalds comments on "unmanageable" AI bug reports for Linux maintainers — r/linux
- ▪ 'Almost entirely unmanageable': Linus Torvalds says AI bug hunters have ruined Linux security mailing list — TechRadar
- ▪ Linus Torvalds says Linux security list is becoming ‘unmanageable’ due to AI bug reports — The Verge
- ▪ Linus Torvalds says AI bug reports have made the Linux security mailing list 'almost entirely unmanageable' — flood of duplicate vulnerability reports prompts switch to public disclosure — Tom's Hardware
- ▪ Linus Torvalds says AI-powered bug hunters have made Linux security mailing list ‘almost entirely unmanageable’ — r/cybersecurity
- ▪ In his weekly Linux kernel post, Linus Torvalds says "AI tools are great" but the flood of duplicate AI bug reports has made the security list "unmanageable" (Simon Sharwood/The Register) — Techmeme
- ▪ Linus Torvalds says AI-powered bug hunters have made Linux security mailing list ‘almost entirely unmanageable’ — r/technology
- ▪ Linus Torvalds says AI-powered bug hunters have made Linux security mailing list ‘almost entirely unmanageable’ — theregister
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,327 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 | Lkml |
| Canonical URL | https://lkml.org/lkml/2026/5/17/896 |
| Publication time | Tue, 19 May 2026 07:04:10 +0000 |
| Retrieval time | 2026-05-19T07:19:57.398Z |
| Last seen | 2026-05-19T07:19:57.398Z |
| 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 | lkOqU8JWGAJr · 9 stories |
| 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
Making sure you're not a bot! Loading...You are seeing this because the administrator of this website has set up Anubis to protect the server against the scourge of AI companies aggressively scraping websites. This can and does cause downtime for the websites, which makes their resources inaccessible for everyone.Anubis is a compromise. Anubis uses a Proof-of-Work scheme in the vein of Hashcash, a proposed proof-of-work scheme for reducing email spam. The idea is that at individual scales the additional load is ignorable, but at mass scraper levels it adds up and makes scraping much more expensive.Ultimately, this is a placeholder solution so that more time can be spent on fingerprinting and identifying headless browsers (EG: via how they do font rendering) so that the challenge proof of…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Lkml.
Discussion
0 commentsMore from Lkml
