Fetching from the wire…
Top 5 · 2026-07-24 · source-backed
On July 22, Codeberg's membership voted 358-144 to amend the Terms of Use, prohibiting projects that "mostly consist of code written by" generative AI. Roughly 50% turnout, 14 abstentions. A second motion committed the forge to never train models on hosted code or user data.
The interesting part isn't the vote. It's the stated driver, which is economic rather than ideological. SSD costs went from roughly €700 each to €3,700. Autonomous agent-built repos burn storage and CI at a rate the forge's funding model wasn't built for.
That reframes the whole thing. Most coverage read this as a values statement about AI-written code. Codeberg is a nonprofit paying hardware bills, and the marginal cost of hosting a repo that a human never reads went up 5x while the volume of such repos went up a lot more.
Enforcement matters here and is getting misreported. The line is "mostly consists of." Human-driven projects that occasionally accept LLM contributions are explicitly safe. This is not a purge of anything touched by a model. If you host agent-assisted work on Codeberg, you're probably fine. If you're mass-generating repos, you're the target, and you're the reason.
The context nobody's connecting: this landed days after Codeberg's July 2 cryptocurrency ban, and together they produced a widely-read "I regret migrating to Codeberg" post that hit 431 points on Hacker News July 24. A forge that makes two content-policy decisions in three weeks is a forge people start reading as unpredictable, regardless of whether each decision is defensible.
Now read this against the Nikkei analysis that surfaced the same days: Alphabet, Microsoft, Amazon, Meta and Oracle carrying roughly $1.65 trillion in off-balance-sheet AI obligations, 122% of the ~$1.35T they actually report. Oracle alone at about $273.3B, up more than 2,900% in four years, with S&P cutting it to BBB- on July 9. Same week Alphabet raised 2026 capex guidance to $195-205B, pushing capex-to-revenue to 41% from 23% a year ago.
At the top of the stack, infrastructure cost is a strategic bet financed with structures accounting press is now comparing to Enron SPVs. At the bottom, it's a nonprofit forge voting on whether it can afford the drives. Everyone shipping more agent output has a bill attached, and it arrives at very different places.
Each link below shares sources, entities, or timing with this story.
Microsoft competes with OpenAI / Shared entities / Earlier coverage
Linked by a graph relationship (Microsoft competes with OpenAI); both cover Amazon, Meta, Microsoft, Oracle; earlier Amazon coverage from 2026-02-26.
Meta released Muse Spark / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Meta released Muse Spark); both cover Everyone, July, Meta; overlapping topics (july, model).
Microsoft released Copilot / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Microsoft released Copilot); both cover July, LLM, Same; overlapping topics (code, repo).
Microsoft competes with OpenAI / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Microsoft competes with OpenAI); both cover LLM, Roughly, Same; overlapping topics (cost, model).
Linked by a graph relationship (Microsoft competes with OpenAI); both cover Everyone, Meta, Roughly; overlapping topics (each, model).
Meta invested in Alphabet / Shared entities / Earlier coverage
Linked by a graph relationship (Meta invested in Alphabet); both cover Alphabet, Amazon, Meta, Microsoft; earlier Alphabet coverage from 2026-07-20.
Microsoft criticizes Claude Code / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Microsoft criticizes Claude Code); both cover July, Same; overlapping topics (code, cost, model, repo).
Microsoft uses AWS / Shared entities / Earlier coverage / Tension
Linked by a graph relationship (Microsoft uses AWS); both cover Amazon, Meta, Microsoft; earlier Amazon coverage from 2026-04-30.