The Tragic Alley of the LLM
The Tragic Alley of the LLM 27 September 2026 The attacker and the defender download the same weights. One of them is already using them to get past the other's web application firewall; the other, as of this month, cannot use them in the place where it would matter. Two earlier articles on this blog worked through the evidence for that (what the measurements say, what can be done anyway).
- ▪The Tragic Alley of the LLM 27 September 2026 The attacker and the defender download the same weights.
- ▪One of them is already using them to get past the other's web application firewall; the other, as of this month, cannot use them in the place where it would matter.
- ▪Two earlier articles on this blog worked through the evidence for that (what the measurements say, what can be done anyway).
Hacker News (AI / LLM) files mainly under ai. We currently carry 6,627 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 | Nikotak |
| Canonical URL | https://nikotak.com/tragic-alley-of-the-llm.html |
| Publication time | Sun, 27 Sep 2026 15:55:43 +0000 |
| Retrieval time | 2026-09-27T17:06:17.892Z |
| Last seen | 2026-09-27T17:06:17.892Z |
| 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 | 3iESDOYc5MbL · 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
The Tragic Alley of the LLM 27 September 2026 The attacker and the defender download the same weights. One of them is already using them to get past the other's web application firewall; the other, as of this month, cannot use them in the place where it would matter. Two earlier articles on this blog worked through the evidence for that (what the measurements say, what can be done anyway). This one is about why the asymmetry exists, where it holds, where it does not, and why the way out is the same in every case. The short version: the asymmetry is not about who has the model. It is about the time budget of the decision. An attacker uses the model offline, needs one success out of many attempts, pays nothing for a wrong guess, and gets to iterate against a defence he can observe.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Nikotak.
Discussion
0 commentsMore from Nikotak
