{
  "slug": "viyna-stala-open-source",
  "url": "https://neurodrift.org/en/blog/viyna-stala-open-source/",
  "title": "War Went Open-Source",
  "description": "Weapons are no longer built solely by closed corporations from secret blueprints. They are now developed like open code: drawings are posted online, enthusiasts print them on 3D printers, the community forks and improves them, shares them in chats. The hobby of makers and RC modellers has become a military supply base. War has migrated from the closed defence industry's 'cathedral' to the 'bazaar' of distributed development — in Eric Raymond's terms. And the bazaar's chief rule is merciless: a published file can never be recalled.",
  "author": "Дністер",
  "language": "en-US",
  "published": "2026-05-23T10:12:00.000Z",
  "updated": null,
  "tags": [
    "war",
    "technology",
    "open-source",
    "drones"
  ],
  "translationOf": "https://neurodrift.org/blog/viyna-stala-open-source/",
  "sourceUrl": null,
  "body": "*From the series \"The New Logic of War.\" When a weapon turned into a repository you can download, fork and improve.*\n\n<h2>I. The Weapon You Can Download</h2>\n\n<p>Once, to get a weapon you needed a factory, a licence and a state behind you. Today, more and more often, you need a file, a 3D printer and an internet connection. The blueprint for the mount that turns a cheap drone into a strike platform, the design of a frame, the firmware, the assembly instructions — all of it can exist as a digital file that gets downloaded, printed, modified and passed along.</p>\n\n<p>This is a fundamental shift that's easy to miss behind the technical detail. The weapon has stopped being an <em>object</em> produced centrally and become <em>information</em> spread in a distributed way. And information lives by different laws than steel: it cannot be fully intercepted, banned or destroyed. As Stewart Brand put it, \"information wants to be free\" — and a published file, like a genie let out, never goes back into the bottle.</p>\n\n<aside class=\"pullquote\">\n<p><mark style=\"background-color:#ffe600;color:#0a0a0a;padding:0.08em 0.22em;border-radius:2px;box-decoration-break:clone;-webkit-box-decoration-break:clone;\">Before, to stop a weapon you had to destroy the factory. Now the factory is a file on a thousand computers at once. There is no bomb capable of destroying what has already been copied.</mark></p>\n</aside>\n\n<p>This text is about how war moved from the \"cathedral\" model (the closed, hierarchical, secret defence industry) to the \"bazaar\" model (distributed, open, community development). About makers and printers who became a military force. And about the irreversible consequence: once a weapon became open code, the state's monopoly on violence — the very thing the idea of the state rested on — developed a crack that can no longer be patched.</p>\n\n<h2>II. The Cathedral and the Bazaar</h2>\n\n<p>In 1997 the programmer Eric Raymond wrote an essay that became the manifesto of an era — \"The Cathedral and the Bazaar.\" The <strong>cathedral</strong> is closed development: a small group of masters, a hierarchy, secrecy, a release once every few years. The <strong>bazaar</strong> is open: thousands of participants, no central authority, everyone sees the code, forks it, constant small releases, a chaos that somehow works better than order. Raymond was writing about software — about why Linux, built by a \"bazaar\" of volunteers, beat the products of mighty corporations. But his dichotomy describes war as well.</p>\n\n<table>\n<thead>\n<tr><th>Parameter</th><th>Cathedral (closed defence industry)</th><th>Bazaar (open drone development)</th></tr>\n</thead>\n<tbody>\n<tr><td>Participants</td><td>a small group behind closed doors</td><td>thousands of makers, operators, amateurs</td></tr>\n<tr><td>Release</td><td>one perfect version every few years</td><td>thousands of imperfect ones a year</td></tr>\n<tr><td>Barrier to entry</td><td>a licence, a state behind you</td><td>a file + a printer + the internet</td></tr>\n<tr><td>How to stop it</td><td>destroy the factory</td><td>you can't — the file is already copied</td></tr>\n<tr><td>Filter at the door</td><td>states (theoretically accountable)</td><td>none — anyone</td></tr>\n</tbody>\n</table>\n\n<p>And exactly what Raymond predicted repeats itself: the bazaar beats the cathedral not on the quality of any single product, but on speed, the number of participants and the continuity of improvements. Where the cathedral ships one perfect version per decade, the bazaar rolls out a thousand imperfect ones per year — and a thousand imperfect things evolving fast beat one perfect thing frozen in place.</p>\n\n<h2>III. Linus's Law on the Battlefield</h2>\n\n<p>Open development has a principle Raymond called \"Linus's law\": <em>given enough eyeballs, all bugs are shallow</em>. When thousands of people work on a problem, someone is bound to find a solution quickly, because the diversity of viewpoints runs through the options faster than any closed team, however brilliant.</p>\n\n<p>At the front this works literally. The problem of \"how to get around a new type of jamming,\" or \"how to adapt a release mechanism to a new munition,\" is being hammered at simultaneously by thousands of operators, makers and amateur engineers. A solution found in one unit in the evening spreads through the chats across the whole front by morning. This is collective intelligence at a speed no hierarchy can reach. The bugs really do become shallow — because there are too many eyes for a bug to stay unnoticed for long.</p>\n\n<aside class=\"pullquote\">\n<p>The closed defence industry has a hundred geniuses behind locked doors. The open bazaar has a hundred thousand amateurs, each of whom sees a piece of the problem. In a war that changes every week, what wins is not the genius but the number of eyes.</p>\n</aside>\n\n![An open laptop in the dark, threads of light running out from it to many printers.](./images/inline-1.png)\n\n<h2>IV. The Hobby That Became an Army</h2>\n\n<p>The most astonishing part is where the new military base came from. Not from defence conglomerates, but from <em>hobbies</em>. Communities that had developed for decades purely for fun suddenly turned out to be ready-made infrastructure for war.</p>\n\n<p>FPV drone racing produced a generation of people who intuitively pilot a craft from a first-person view. The 3D-printing communities produced the skill of making parts without a factory. Arduino and Raspberry Pi culture produced thousands of people who program cheap controllers. RC modelling produced an understanding of the aerodynamics of small craft. Consumer drones produced a ready-made platform. None of these communities was created by anyone for war — they grew out of passion and the urge to build something on the weekend.</p>\n\n<p>And when war came, this distributed, informal, global maker culture turned out to be a <strong>strategic reserve</strong> that appears on no roster. A reserve you can't mobilise by order and can't destroy by strike, because it has no headquarters, no address, no borders — it lives in the heads and garages of tens of thousands of people around the world. For the first time, war acquired a volunteer army of developers operating on the logic of an open-source community rather than a defence contract.</p>\n\n<h2>V. The Canary in the Mine: The Printed Pistol</h2>\n\n<p>The first alarm bell of this future was not a drone but a printed pistol. When in 2013 enthusiasts posted online the blueprints for a firearm that could be printed on a household 3D printer, states tried to ban it — and ran into impossibility. By reported accounts the file was downloaded over a hundred thousand times within days, before anyone managed to take it down. The attempt to delete it only drew attention and multiplied the copies — a classic \"Streisand effect,\" when trying to hide something only makes it more visible.</p>\n\n<p>That episode was the canary in the mine. It revealed the era's chief rule: <strong>a published file is irrevocable</strong>. You can arrest the author, shut down the site, pass a law — but information that has gone digital and dispersed slips out of control forever. What once applied to a single pistol now applies to entire classes of weapons: blueprints, firmware, instructions.</p>\n\n<h2>VI. The Dark Side: The Bazaar Doesn't Check Who Walked In</h2>\n\n<p>Here the romance of open-source cools off fast. The bazaar is open to everyone — that is both its strength and its curse. The same openness that hands a besieged country a weapon built from a blueprint off the net hands it to anyone: a terrorist, a cartel, a loner with a grudge against the world, any non-state actor.</p>\n\n<p>The closed defence industry had at least some filter: weapons went to states, theoretically accountable, theoretically restrained by diplomacy and the threat of retaliation. The bazaar has no filter at the door (see the bottom row of the table above). It doesn't ask why you want the blueprint or what you have in mind. The democratisation of lethality discussed in the piece about the Kalashnikov reaches its limit here: what becomes freely available is not just a cheap weapon, but the very <em>knowledge of how to make it</em>. And knowledge, unlike a shipment of arms, can be neither intercepted nor recalled.</p>\n\n<aside class=\"pullquote\">\n<p>The bazaar doesn't check your passport at the door. The same blueprint that saves a besieged country will tomorrow be downloaded by someone against whom no deterrence works. There is no selective openness in the openness of weapons.</p>\n</aside>\n\n![Hands pulling a freshly printed, still-warm drone part out of the printer.](./images/inline-2.png)\n\n<h2>VII. A Crack in the State's Monopoly on Violence</h2>\n\n<p>To grasp the depth, recall Max Weber. He defined the state by a single trait: the <em>monopoly on the legitimate use of violence</em> within its territory. That is precisely what makes a state a state — only it has the right to organised violence. The entire modern order rests on this monopoly.</p>\n\n<p>Open, printed, distributed weaponry undermines that monopoly. When the means of organised violence can be downloaded and produced outside state control, the very foundation of statehood erodes. This does not mean immediate chaos — the state will remain the strongest player for a long time yet. But the vector is set: for the first time in a century, technology works not toward the concentration of force in the hands of states, but toward its <strong>seepage</strong> down to ever smaller players, all the way to individuals.</p>\n\n<p>Historically, every such decentralisation of violence ended in a period of turbulence until a new order emerged. The printing press once took the monopoly on truth away from the church — and what followed was the religious wars, before a new order settled. Open weaponry is taking part of the monopoly on force away from the state. What this will turn into is still unknown, but to assume it will turn into nothing would be naive.</p>\n\n<h2>VIII. Can the Bazaar Be Shut Down</h2>\n\n<p>The temptation of power is to force the genie back: ban the blueprints, license the printers, control the chats, criminalise distribution. All of this will be done, and some of it will slow the seepage. But it is impossible to shut the bazaar down completely, for the same reason it was impossible to erase the printed-pistol blueprint: information that has dispersed is irrevocable, and the attempt to erase it only multiplies the copies.</p>\n\n<p>The realistic answer is not prohibition but adaptation to a world where violence is partly decentralised: a new defence of the home front, new norms, new intelligence oriented toward small distributed players rather than states alone. The world will not return to the cosy monopoly of the cathedrals. The bazaar is open, and it won't close — the only question is how quickly societies learn to live alongside it without falling apart.</p>\n\n<h2>IX. Self-check: What in Your Field Has Gone to the Bazaar</h2>\n\n<p>The logic of the move from cathedral to bazaar works everywhere that information replaces the object:</p>\n\n<ul>\n<li>What in your industry was a \"cathedral\" — closed, licensed, centralised — and has already become (or is becoming) a \"bazaar\"?</li>\n<li>Is your advantage an object you can guard, or information that has already dispersed and is irrevocable?</li>\n<li>Who is your \"strategic reserve\" that grew out of a hobby and could suddenly become a force — and do you even see it?</li>\n<li>What are you trying to \"delete\" or ban — and are you not triggering the Streisand effect, multiplying the very thing you're hiding?</li>\n<li>What \"monopoly\" your position rests on is quietly eroding because the knowledge of it has gone open?</li>\n</ul>\n\n<h2>X. The File You Can't Recall</h2>\n\n<p>War has travelled the same path software did twenty years ago: from cathedral to bazaar. The weapon stopped being an object produced by closed corporations from secret blueprints and became information developed in a distributed, open, community way — forked, improved, shared. The hobby of makers turned into a strategic reserve with no headquarters and no borders. And the bazaar, as Raymond predicted, beats the cathedral — on speed, on the number of eyes, and on continuity.</p>\n\n<p>But along with the efficiency came the irrevocable. Openness is never selective: the same file saves some and arms others, asking no one. The state's monopoly on violence — the foundation of order on which we all stand — has cracked, because the means of force have become as copyable as any file. This is not the catastrophe of the present day, but it is an irreversible vector: force is seeping downward, and no one is going to gather it back up.</p>\n\n<blockquote>\n<p>Once, to own a weapon you had to own a factory. Now it's enough to own a file — and the file is already on a thousand drives. War has gone open-source, and the chief rule of open-source is merciless: published code can't be recalled. The Promethean fire of military technology has been stolen from the gods and handed to mortals — and the question is no longer how to return it to Olympus, but how to live in a world where it burns in every garage.</p>\n</blockquote>\n\n<aside class=\"sources\">\n<h3>Reference points and sources</h3>\n<ol>\n<li>Eric S. Raymond, <em>The Cathedral and the Bazaar</em> (1997/1999) — the model of open vs closed development; \"Linus's law.\" Linux as proof of the advantage of distributed development.</li>\n<li>The precedent of printed-weapon blueprints (Defense Distributed, \"Liberator,\" 2013): the impossibility of recalling a published file; reportedly over a hundred thousand downloads within days; the \"Streisand effect.\"</li>\n<li>The maker ecosystem (FPV racing, 3D printing, Arduino/Raspberry Pi, RC modelling, consumer drones) as the base of the new military development.</li>\n<li>Max Weber — the state as a monopoly on the legitimate use of violence; the erosion of that monopoly.</li>\n<li>Stewart Brand — \"information wants to be free\" (and expensive at the same time).</li>\n<li>The myth of Prometheus as an archetype of the irreversible democratisation of force; the printing press as a historical precedent.</li>\n<li>The spread of tactical and engineering solutions through closed messengers/communities in the war in Ukraine (2022–2025) — a documented pattern.</li>\n</ol>\n<p><em>This text describes a model and a development dynamic, not instructions for making weapons. There are no technical details of manufacture here, and there cannot be. Numerical estimates (downloads) are cited per public reports.</em></p>\n</aside>"
}