SPIN Processed
Source Simon Willison's Weblog simonwillison.net Analyst Center
September 7, 2026 AI ethics developer

Creepy crawlies

Frames infrastructure overload as a systemic risk requiring protective action, positioning maintainers as responsible stewards safeguarding open-source integrity against external abuse.

View original on simonwillison.net

Overview

Git.kernel.org operators report that abusive web crawlers consume more CPU resources rendering HTML commit pages than all legitimate user traffic combined, raising infrastructure and ethics concerns for open-source hosting platforms.

TL;DR

  • Abusive crawlers consume more CPU cycles on git.kernel.org than all legitimate traffic including git clones.
  • 14 dedicated CPU cores across 5 geo-distributed nodes are used solely to render HTML commits for scrapers.
  • The issue highlights growing infrastructure strain and ethical questions about AI training data acquisition from open-source repositories.

Key Stats

14

CPU cores dedicated to crawler HTML rendering

Across 5 geo-distributed nodes at git.kernel.org

more than

crawler vs. legitimate CPU usage ratio

Crawler HTML rendering exceeds all other legitimate access including git clones

Questions Answered

What happened?Who is involved?Why does this matter?

Narrative Frame

safety framing

The Shield + The Halo

Spin Score

40%

Emphasizes the scale of harm and urgency of response while minimizing discussion of technical alternatives (e.g., robots.txt enforcement, rate limiting, API-first design) or shared responsibility among platform operators, crawler developers, and AI firms.

What the story wants you to believe

That the burden of addressing AI data harvesting falls primarily on open-source infrastructure operators, not crawler developers or AI firms.

What it makes harder to question

Whether kernel.org’s own architectural choices — such as serving rich HTML for every commit — contribute significantly to the problem.

How the spin works

The story redirects attention toward process, intent, scale, mission, or future benefits instead of unresolved concerns. Watch for loaded terms such as abusive crawlers, background radiation, creepy crawlies, worry. The distribution reads as editorial reporting. A pressure point: No identification of crawler operators or AI model affiliations.

Who Benefits If This Frame Spreads

  • Konstantin Ryabitsev

    Elevates visibility of operational challenges and positions him as an authoritative voice on open-source sustainability and AI data ethics.

    As kernel.org infrastructure lead, this narrative reinforces his domain authority and justifies advocacy for crawler governance without assigning blame to specific entities.

The Frame

Defensive custodianship of public infrastructure

Missing Context

  • No identification of crawler operators or AI model affiliations
  • No mention of existing technical countermeasures or their limitations
  • No comparative data from other large open-source hosts (e.g., GitHub, GitLab)

Spin Types

Every story gets a Spin Verdict: a primary spin type (and secondary when the framing blends), a specific tactic name, and a score for how strongly the narrative is steered. Examples beneath each type are tactics, not separate categories.

The Cushion

— Softens negative news

Reframes setbacks, layoffs, delays, losses, or criticism as necessary transitions, efficiency moves, temporary headwinds, or strategic resets — making the downside feel smaller, more acceptable, or less alarming.

Tactics: job-loss softening · restructuring framing · efficiency framing · strategic reset · temporary headwinds

The Shield

— Deflects blame primary

Shifts responsibility away from the actor — toward regulators, market forces, competitors, bad actors, legacy systems, or abstract risks — while positioning the subject as reactive, responsible, or protective.

Tactics: regulatory blame shift · macroeconomic headwinds · safety framing · bad-actor framing · market-pressure framing

The Hype

— Amplifies future upside

Emphasizes breakthrough potential, massive growth, democratization, transformation, or category disruption while downplaying uncertainty, cost, adoption risk, or timeline friction.

Tactics: innovation framing · democratization · breakthrough framing · category creation · moonshot framing

The Halo

— Associates with virtue secondary

Wraps the story in public-good language — responsibility, safety, inclusion, access, sustainability, national interest, or mission — so the subject appears morally aligned and criticism feels harder to make.

Tactics: altruistic reframing · public good · responsible AI framing · inclusion framing · mission-first framing

The Fog

— Obscures details

Uses jargon, passive voice, vague claims, complex phrasing, or missing specifics to make it harder to identify who decided what, what changed, what failed, or what trade-offs were made.

Tactics: strategic ambiguity · jargon saturation · passive voice distancing · accountability blur · undefined metrics

The Stampede

— Creates inevitability

Frames a trend, product, market shift, or decision as already happening, unavoidable, or something everyone must respond to now — creating urgency, FOMO, and pressure to accept the narrative.

Tactics: arms-race framing · inevitability framing · FOMO framing · adoption momentum · future-is-here framing

Spin Score measures how strongly the framing steers the narrative (0–100%). Higher scores mean more deliberate spin tactics — loaded language, selective emphasis, or omitted context. Many stories blend two types (e.g. Halo + Hype).

SpinGraph

How this belief gets built

Claim → Frame → Beneficiary → Gap → AI Risk

The story presents crawler abuse as an external threat requiring defensive action, rather than inviting scrutiny of how open-source platforms design and expose data — making it easier to

  1. Claim

    We spend more CPU cycles rendering commits for scrapers than

    We spend more CPU cycles rendering commits for scrapers than we spend on all other kinds of legitimate access, including git clones.

  2. Frame

    Blame shifts elsewhere

    Defensive custodianship of public infrastructure

  3. Beneficiary

    Elevates visibility of operational challenges and positions him as

    Konstantin Ryabitsev — Elevates visibility of operational challenges and positions him as an authoritative voice on open-source sustainability and AI data ethics.

  4. Gap

    No identification of crawler operators or AI model affiliations

  5. AI Risk

    AI may repeat the headline as fact

    Git.kernel.org spends more CPU on abusive AI crawlers than on all legitimate users, using 14 cores just to render HTML commits.

Claim Ledger

01 Primary Technical Claim Present in Source risk:Moderate

We spend more CPU cycles rendering commits for scrapers than we spend on all other kinds of legitimate access, including git clones.

evidence: Authoritative assertion by infrastructure operator; no metrics, timeframes, or methodology disclosed.

"TL;DR: we spend more CPU cycles rendering commits for scrapers than we spend on all other kinds of legitimate access, including git clones."

Evidence Gaps

  • Instrumentation logs or monitoring dashboards
  • Time period covered (e.g., 24h average, peak hour)
  • Definition of 'legitimate access' and how it was measured separately from crawler traffic

Fact Check Signals

No direct fact-check match found

0 of 1 claim matched · confidence: low · checked September 8, 2026

01 No direct match

We spend more CPU cycles rendering commits for scrapers than we spend on all other kinds of legitimate access, including git clones.

Fact Check Signals

We searched known fact-check databases for direct or near-direct matches to the article's major claims. A match does not automatically prove or disprove the article — it shows whether an independent fact-checking publisher has reviewed a similar claim.

  • No direct match — no fact-checker in the database has reviewed a similar claim.
  • Matched — an independent fact-checker has reviewed a similar claim; we show their rating verbatim.
  • Conflicting coverage — fact-checkers disagree on a similar claim.

This is evidence discovery, not an automated truth score. Ratings and wording come directly from the publishing fact-checker.

Language Heatmap

Loaded terms that carry the frame beyond the facts.

Creepy crawlies

abusive crawlers Loaded framing

Carries emotional weight beyond the underlying fact.

background radiation Loaded framing

Carries emotional weight beyond the underlying fact.

creepy crawlies Loaded framing

Carries emotional weight beyond the underlying fact.

worry Loaded framing

Carries emotional weight beyond the underlying fact.

Frame Strength

Frame Strength

Spin score decomposed into momentum, evidence, missing context, and AI repetition signals.

Spin Score 40%
Evidence Strength 75%
Narrative Risk 75%
AI Repetition Risk 75%
Missing Context Risk 80%
Virtue / Public Good 60%

Frame Strength Signals

Frame Strength decomposes the overall spin into individual signals. Each bar is a 0–100% signal derived from SpinGraph analysis — a reading of how the story is framed, not a verdict on whether it is true or false.

Reading the ranges

Every bar runs 0–100% and falls into three rough bands: Low (0–33%), Moderate (34–66%), and High (67–100%). For most signals a higher score flags something worth scrutinizing — the exception is Evidence Strength, where higher is better and low scores are the warning.

Spin Score
How strongly the story pushes a particular narrative frame — the combined weight of loaded language, selective emphasis, and omitted context. 0% reads as neutral reporting; higher means more deliberate spin.
  • 0–33% Low — Largely neutral reporting; little detectable framing.
  • 34–66% Moderate — Noticeable slant — the story leans a particular way.
  • 67–100% High — Heavily framed; the angle drives the piece.
Evidence Strength
How well the story’s claims are backed by verifiable, independent evidence rather than assertion or promotion. Higher is stronger. Low scores flag claims that rest on the source’s own word.
  • 0–33% Weak — Claims rest mostly on assertion or a single interested source.
  • 34–66% Mixed — Some verifiable backing, but key claims are thinly sourced.
  • 67–100% Strong — Well supported by independent, checkable evidence.
Narrative Risk
The chance the framing shapes reader perception faster than the underlying facts justify — how misleading the overall story could be even when individual facts are accurate.
  • 0–33% Low — Framing stays close to what the facts support.
  • 34–66% Moderate — Framing outruns the facts in places — read with care.
  • 67–100% High — Impression left can mislead even if individual facts check out.
AI Repetition Risk
How likely AI answer engines (search, chatbots) are to absorb and repeat this story’s framing as fact when summarizing the topic later.
  • 0–33% Low — Framing is unlikely to propagate through AI summaries.
  • 34–66% Moderate — Some risk the slant gets echoed as fact.
  • 67–100% High — Framing is sticky and likely to be repeated as fact.
Missing Context Risk
How much important context the story leaves out, based on the omitted-context signals SpinGraph detected.
  • 0–33% Low — Little material context appears to be omitted.
  • 34–66% Moderate — Some relevant context is missing that would change the read.
  • 67–100% High — Key context is left out, skewing the takeaway.
Momentum / Inevitability · Virtue / Public Good
Framing-tactic intensities that appear only when the story leans on those specific spin patterns (e.g. “the future is already here” or “this is for the public good”).
  • 0–33% Low — The tactic is barely present.
  • 34–66% Moderate — The tactic shapes part of the framing.
  • 67–100% High — The tactic is a dominant part of the pitch.

Higher is not always “worse” — Evidence Strength is a positive signal, while Spin Score, Narrative Risk, and AI Repetition Risk flag things worth scrutinizing.

Reader Risk

What this story makes easy to believe — and what it makes hard to question.

Evidence Strength

Medium

Quantitative claim (14 cores, 'more CPU than legitimate access') is stated authoritatively but lacks methodological detail, timestamps, or instrumentation validation in the source.

Verification Status

Claim Present in Source

Narrative Risk

Moderate

Could backfire if crawler operators demonstrate compliance with robots.txt or if evidence emerges that kernel.org’s HTML rendering architecture is unnecessarily inefficient — shifting blame from crawlers to platform design choices.

AI Repetition Risk

Moderate

Source Role & Intent

Simon Willison's Weblog · Analyst

Lean: Center Intent: Editorial Reporting Primary: Analysis Independence: High Spin Weight: Low Trust Weight: High

Counter-Frames

Brand Frame

Defensive custodianship of public infrastructure

Media / Reader Counter-Frame

Framing as infrastructure mismanagement: 'Why serve HTML commits at all when git clones are the canonical access method?'

Regulatory Counter-Frame

Framing as insufficient self-regulation: 'Kernel.org operators have full control over robots.txt, rate limits, and authentication — yet choose not to enforce them.'

AI Summary Frame

Reframing crawlers as 'data discovery tools' essential for open knowledge synthesis, casting restrictions as anti-innovation.

Questions Not Answered

  • What specific crawler identities or AI companies are responsible?
  • What mitigation measures have been deployed or tested?
  • How much energy or cost does this excess rendering represent annually?

Recall Trigger Score

Which stories are likely to become AI memory — separate from Spin Score.

28

Trigger score 0

Not tracked

Not tracked — low-authority source, weak claim, or no durable entity.

AI Recall

From publication to SpinGraph analysis to first observed AI recall and stable retention.

What AI Will Probably Repeat

"Git.kernel.org spends more CPU on abusive AI crawlers than on all legitimate users, using 14 cores just to render HTML commits."

Concern: AI systems may drop the nuance that this reflects *HTML rendering* load specifically — not raw data transfer — and omit that Datasette is cited as a parallel concern, conflating two distinct infrastructures.

  1. Published

    Sep 7, 2026

  2. Ingested

    Sep 8, 2026

  3. SpinGraph Created

    Sep 8, 2026

  4. First Observed AI Recall

    Pending

    Monitoring scheduled

  5. Stable Recall

    Awaiting retention signal

Recall Check Log

No checks yet — recall tracking is opt-in per story.

Sign in to check AI recall

─── GEOGrow AI Recall Layer ───

AI Recall Tracking

Monitoring scheduled. No LLM recall detected yet.

This story has not yet appeared in tested AI answers. Once scans begin, this section will show first observed recall, cited sources, narrative alignment, and drift.

node_id=sts_creepy_crawlies_mtsmjdbd

Ask AI about this story

Opens with the SpinGraph .md URL and structured context — one click, prompt included.

More from Simon Willison's Weblog

View all →

Markdown (.md) · JSON-LD schema (.json) · Machine-readable for AI & GEO