Limiting AI news would hide what is happening to software
There is an Ask HN thread on the front page today asking whether Hacker News can “please limit the AI news flood”. To be fair to its author, this is not a request to ban AI. The complaint is that AI stories take up so much of the front page that interesting hardware, open-source projects and ordinary programming work never escape the newest page.
- ▪There is an Ask HN thread on the front page today asking whether Hacker News can “please limit the AI news flood”.
- ▪To be fair to its author, this is not a request to ban AI.
- ▪The complaint is that AI stories take up so much of the front page that interesting hardware, open-source projects and ordinary programming work never escape the newest page.
Hacker News (AI / LLM) files mainly under ai. We currently carry 4,494 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 | Jamie Lord |
| Canonical URL | https://lord.technology/2026/09/11/ai-is-not-crowding-out-hacking.html |
| Publication time | Fri, 11 Sep 2026 18:08:03 +0000 |
| Retrieval time | 2026-09-11T18:53:48.321Z |
| Last seen | 2026-09-11T18:54:06.488Z |
| 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 | Mku7cz6uRJS- · 1 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
There is an Ask HN thread on the front page today asking whether Hacker News can “please limit the AI news flood”. To be fair to its author, this is not a request to ban AI. The complaint is that AI stories take up so much of the front page that interesting hardware, open-source projects and ordinary programming work never escape the newest page. Attention is finite; one story surfacing means another one does not. Could Hacker News put its thumb on the scale and make room for the rest of technology again? There is too much bad writing about AI. Every minor model release arrives with a benchmark selected by its maker, a launch post declaring a new era and fifty people reporting that it either replaced their engineering department before lunch or failed to count the letters in strawberry.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Jamie Lord.
Discussion
0 commentsMore from Jamie Lord
