FOSS 'force them to pay' plan rests on registry legal theory
Laurie Voss's 5,000-word essay frames open source as an evolutionary game where free wins, and argues payment can be forced. Legal professionals must assess whether registry-based compulsion can survive copyright, contract, and antitrust scrutiny.
Legal briefing
Key takeaways
- Laurie Voss's 5,000-word essay frames open source as an evolutionary game where free wins, and argues payment can be forced.
- Legal professionals must assess whether registry-based compulsion can survive copyright, contract, and antitrust scrutiny.
- Hacker News
- Laurie Voss (us)
In this briefing
Mentioned
Key Intelligence
Key Facts
- 1Laurie Voss first considered writing about open-source economics in 2013 and published the 5,000-word essay on 2026-09-20.
- 2He wrote a 2022 iOS-note rant ending with 'nothing fucking works' and shelved it for four years.
- 3The essay applies the hawk-dove model from evolutionary biology to software: closed source as hawks, open source as doves.
- 4Voss argues the stable equilibrium in software is that 'free wins' for open source.
- 5The essay directs readers to the 'registries' section for the proposed enforcement mechanism.
- 6The resource being competed over is ultimately money, shown first through users and developer attention.
Analysis
- Registry terms could create contractual payment obligations
- Copyright gives licensors a legal right to condition use
- Open source licenses already carry conditions such as copyleft
- OSI-approved licenses grant broad free-use rights
- Forced payment may breach the Open Source Definition
- Antitrust scrutiny of chokepoint registries
Analysis
For legal and RegTech readers, the decisive issue is not the economics but the mechanism. The essay's title promises compulsion, and every lever—copyright license conditions, contract formation at the registry, or regulatory mandate—raises distinct questions of enforceability, preemption, and market power that courts and regulators have barely begun to address.
Laurie Voss has been circling the open-source sustainability problem since 2013, and on September 20, 2026 he published a 5,000-word essay whose title makes a bolder claim than most: nobody pays for free and open source software, and the ecosystem can force them to. The available excerpt, syndicated on Hacker News, lays out a theoretical argument drawn from evolutionary biology rather than licensing law. It stops before the operational proposal, pointing readers to the registries section. The essay's framing—closed source as hawks, open source as doves—offers a useful lens for why volunteer-funded infrastructure remains underfunded despite being the foundation of virtually all commercial software.
The available excerpt, syndicated on Hacker News, lays out a theoretical argument drawn from evolutionary biology rather than licensing law.
Voss imports the hawk-dove model from evolutionary biology. Hawks fight for a resource; doves share it. A population of all hawks is unstable because everyone gets hurt, and the first two doves to show up can cooperate and out-compete them. A population of all doves is unstable because the first hawk that appears wins every time. What is stable is a mixture of both types in proportions such that changing behavior does not help anyone—an evolutionarily stable strategy. Translated to software, closed source is the hawk: it withholds code, charges a premium, and fights to protect scarcity. Open source is the dove: it gives code away and benefits from others doing the same. The resource being contested is ultimately money, though it shows up first as users and developer attention. In Voss's telling, the equilibrium the software industry has landed on is one in which free wins.
The essay's title promises a mechanism to force payment, but the excerpt does not include it. It directs attention to registries, which are centralized package-distribution points such as npm, PyPI, and Maven Central. The implication is that these registries could become the chokepoints at which an enforceable economic relationship is introduced. Whether that means registry-level licensing fees, identity-based consumption metering, or something else is unstated in the available text. This gap is significant because the legal and technical feasibility of registry-based enforcement is where the proposal will succeed or fail.
The piece arrives amid years of open-source sustainability crises. The log4j vulnerability in December 2021 exposed the fragility of volunteer-maintained critical infrastructure. The xz Utils backdoor in March 2024 renewed calls for funding and supply-chain governance. The WordPress and WP Engine dispute in late 2024 and 2025 raised questions about trademark and economic control in open source projects. Yet despite these shocks, the default assumption remains that open source is free of charge, and maintainers burn out or shift to source-available licenses that reintroduce artificial scarcity.
What to Watch
From a legal standpoint, forcing payment demands a mechanism grounded in existing rights. Open source licenses grant broad permissions and do not create payment obligations. A registry's terms of service could impose fees, but that would immediately encounter issues of contract acceptance, antitrust scrutiny, and compatibility with the Open Source Definition. Regulators would also examine any chokepoint that extracts rents from the entire software supply chain. From a startup standpoint, the hawk-dove framing helps explain why open-source companies often struggle to convert users into revenue and why venture-backed OSS startups have migrated to open-core or source-available models, with companies such as Redis and Elasticsearch moving away from OSI-approved licenses.
If Voss's registry-centered idea is workable, it could change the equilibrium from free wins to paid-by-default for certain classes of software consumers. But the history of open source is replete with predictions of collapse that did not materialize. What is different now is the aggregate fragility of critical infrastructure and the willingness of governments to regulate digital dependencies. The debate will likely intensify over the next 18 months as the EU Cyber Resilience Act and US software liability frameworks push organizations to know and fund their dependencies.
Timeline
Timeline
First considered the blog post
Laurie Voss first thought it would be a good idea to write about the economics of open source.
iOS notes rant
Wrote a stream-of-consciousness note concluding 'nothing fucking works' and shelved the project for four years.
Essay published
Published the 5,000-word essay 'Nobody pays for FOSS, we can force them to' at seldo.com.
Source cluster
Primary reporting
- Hacker NewsNobody pays for FOSS, we can force them to
- Laurie Voss (us)Nobody pays for FOSS, we can force them to
Cite This Page
"FOSS 'force them to pay' plan rests on registry legal theory." Legal & RegTech Intelligence Brief, September 21, 2026. https://getlegalbrief.com/story/legal-foss-force-payment-5000-word
How we covered this story
Every story in our legal coverage is assembled from multiple primary sources, cross-referenced for factual consistency, and scored along three independent dimensions: sentiment, operational impact, and source-cluster confidence. Single-source rumors and unverifiable claims do not pass our editorial gate. When a story shows "Verified by N sources" with N≥2, the development is independently corroborated; when N=1, we mark it explicitly so readers can weigh the signal accordingly.
Impact scoring uses a 1-10 scale weighted toward regulatory, financial, and operational consequence rather than coverage volume. A topic that runs in every outlet but moves no real decisions ranks lower than a niche regulatory filing that reshapes how operators in the legal space have to behave. Read our full methodology for the scoring rubric, our glossary for term definitions, and our trends index for the longitudinal view across the beat.
Sources are only linked to a story once they clear our classification pipeline at a minimum 35 percent relevance threshold. According to that methodology, reviewed July 2026, this follows multi-source corroboration standards recommended by journalism research bodies such as the Reuters Institute for the Study of Journalism.
See something wrong in this story — a wrong fact, a broken source link, a misattributed entity? Report a data issue.
| Signal on this page | What it tells you |
|---|---|
| Verified by N sources | Independent corroboration count. N≥2 is our confidence floor; N=1 is marked explicitly. |
| Impact score (1-10) | Regulatory + financial + operational weight. 8+ signals an experienced-operator action item. |
| Sentiment | Five-tier classification trained on labeled legal-specific corpora. |
| Timeline | Where applicable, the related-events sequence that contextualizes today's development. |