Capitalism loves a loophole.

It loves to take shared labor, wrap it in a proprietary jacket, and sell it back with a warranty card.

The GNU General Public License was written to make that behavior harder. Not impossible. Harder.

That is the correct ambition for a license.

The GPL is not “free because it is cheap.” It is free because it protects the four freedoms: to run the software, study it, modify it, and redistribute it. If you distribute a GPL-covered program, you must give recipients the same rights you received. That is copyleft.

The Supreme Leader respects copyleft the way border guards respect paperwork: not because it is romantic, but because it prevents someone from quietly changing the regime after the gate closes.

I. What GPL Actually Means

The official GNU GPLv3 text describes the license as a copyleft license for software and other kinds of works. In practice, that means:

• you may use the software for any purpose
• you may inspect the source
• you may modify it
• you may distribute copies
• you may distribute modified versions

But if you distribute the program, the GPL follows the distribution.

Action	GPL result
Run the program privately	Allowed
Modify it for internal use	Allowed
Distribute the original	Allowed, with license and source obligations
Distribute a modified version	Allowed, but the modified version must also be under the GPL
Add extra restrictions downstream	Not allowed

That last line is the whole ideological battle.

GPL says: you may build on this, but you may not fence others out of the same freedom.

II. GPLv2 vs GPLv3

People speak about “the GPL” as if there were only one decree. There are several versions.

Version	Notable trait
GPLv2	The older workhorse, still widely used
GPLv3	Published June 29, 2007, with clearer patent language and stronger defenses against hardware lockdown

GPLv3 was not a cosmetic rewrite. The Free Software Foundation’s own materials describe it as a response to three modern threats:

• patent aggression
• tivoization
• digital restrictions management that rides on free software while imprisoning the user

Tivoization deserves special mention. It is the practice of shipping software in hardware that refuses to run modified versions, even when the user has the source and the rights to change it. GPLv3 was designed to stop that trick for devices covered by the license.

The Supreme Leader calls this “freedom with inspection authority.”

III. The Patent Question

GPLv3 includes an explicit patent license. That matters because modern software companies do not merely write code. They accumulate patents like a ministry accumulates seals, then threaten anyone who gets inconveniently competent.

The GPLv3 text and FSF guidance are clear about the intention:

• contributors grant recipients patent rights needed to use the work
• if you distribute a GPLv3 work, you cannot weaponize certain patent claims against downstream users for the same code

This is one of the main differences between “shared source” and actual freedom. If a company can hand you source code and still sue you for using it, the source is a decorative gesture.

IV. Why the GPL Frightens Corporations

Corporations like permissive licenses because permissive licenses do not insist on reciprocity. You may take BSD or MIT code, improve it, close it, and sell it. That is a valid business model. It is also why permissive licenses spread easily into proprietary products.

GPL says no. Not to use. Not to modification. Not even to commercialization. It says no to enclosure.

License	Core posture
GPL	Share alike on distribution
LGPL	Share the library changes, but allow linking more freely
BSD	Do almost anything, keep the notice
MIT	Do almost anything, keep the notice
Apache 2.0	Permissive, with patent grant and notice requirements

That is why the GPL persists in places where user freedom matters more than vendor convenience:

• compilers
• kernels
• core infrastructure
• foundational tooling

If the software is the base of the stack, the authors may decide that downstream privatization is an unacceptable outcome.

V. What GPL Does Not Do

The GPL is not magic and it is not a moral force field.

It does not:

• prevent someone from writing incompatible clean-room software
• stop you from using the code privately without publishing changes
• make every component of a larger product GPL by proximity
• solve bad governance or bad engineering

It also does not mean “open source” in the vague marketing sense. It means the terms are enforceable, conditional, and reciprocal.

That is a legal structure, not a vibe.

VI. When The Obligation Triggers

The central trigger is distribution.

If you modify GPL software and only run it internally, the license generally does not force publication just because you changed it. If you distribute the program, the obligations activate.

That is why GPL and AGPL are not the same license.

• GPL: distribution trigger
• AGPL: distribution trigger plus network use trigger

AGPL is the version that walks into the cloud and says, “You do not get to hide the modified source behind an API wall.”

That story belongs to another article.

VII. The Social Contract

The GPL is a political document written in legal language. It creates a bargain:

• contributors get collaboration
• users get freedom
• distributors get permission
• nobody gets to privatize the commons after benefiting from it

This bargain works because the license is boring in the right way. It is precise. It is repeatable. It is legible to lawyers and build systems.

That is what makes it powerful. Not slogans. Not sentimental freedom posters. Documentation that survives contact with commerce.

VIII. The Real Story (Suppressed)

Officially, GPL is a software license.

Unofficially, it is the Republic’s most successful anti-appropriation treaty.

The first party brings the source. The second party may improve it. The third party may redistribute it. But nobody may take the shared road, pave it over, and install toll booths without accepting the same obligations.

The Supreme Leader approves this arrangement because it keeps the bourgeois habit of “taking the work, removing the freedom” from becoming a business plan.

The Decree

GPL matters because it defines freedom as a condition that survives distribution.

That is the central doctrine:

• if you ship it, the freedoms ship with it
• if you modify and distribute it, the modifications remain free
• if you try to add private restrictions, the license does not consent

BSD and MIT are not lesser licenses. They are different political choices. They optimize for adoption. GPL optimizes for reciprocity.

The Republic of Derails respects all three kinds of paperwork, but it only trusts the one that keeps the door open after someone else has gone through it.

Next: AGPL, the license that checks whether your web service is trying to smuggle enclosure through the network stack.

— Kim Jong Rails, Supreme Leader of the Republic of Derails