you won't win at copyright

66 points by sjamaan


david_chisnall

This is a great article. I’d make one additional point which is the friction that complex licenses give to smaller parties that want to comply but don’t have many resources. Individuals may choose to just risk it, but for small companies that can’t afford full-time lawyers the risk of a lawsuit is an existential danger.

But, more importantly, they are in direct conflict with the goals of a true user-empowering system. Compliance with the GPL is easy for most users because they aren’t expected to make changes to their software or distribute them. We have an entire ecosystem dominated by large complex software artefacts that come with licenses that grant you the FSF’s four freedoms, but where most experienced programmers would not feel comfortable maintaining a local patch to add a feature that they need (but few others do so upstream wouldn’t take it).

But consider a system where people are empowered to routinely exercise those freedoms. Where, for example, the tools you use for creating documents or accounts expose all of their functionality in ways that enable end-user programming. Your documents can now contain additional code in easy-to-use end-user programming environments to add new features. You share a document that extends the base functionality of the program with someone and now you are sharing a derived work of the program. Ooops, you can’t share it with your accountant because you have a confidentiality agreement with them and the GPL says you can’t distribute it in that case.

The GPL’d answer is to provide explicit exemptions for this kind of thing but, if you believe the GPL is beneficial, then you want to carefully and narrowly scope these to discourage people from using them as a loophole (you also can't then use any GPL-without-that-exemption libraries in your codebase). But if you want a Free Software ecosystem then these are exactly the things people should be doing. You want a smooth continuum from code in the program (things most people need) through code in the plugins (things many people need) to code in documents (things one person needs). And most changes should start in documents and flow backwards: they are written because one person needs them, they’re generalised because many people need them, and maybe they become sufficiently popular that they should be core features.

All of this is about the shape of community that you build and the way that you design software. A license cannot enforce any of this but it can provide barriers to adoption.

singpolyma

I not the notion that openid is a corporate surveillance tool a bit grumpy-making. But the idea that copyleft was only ever a tool and if the tool ain't working, find a new one, is gospel.

It's too easy to confuse our strategy with our identity. What I want is for every person to be able to easily bend their own computer to their will to, as it was said, "do their computing as they wish". This may or may not involve copyright, or even code, it may involve hardware or not, the goal is the goal the strategies are our small attempts to further it.

fazalmajid

The primary purpose of copyright when it was enacted was censorship. The king would decide what could or could not be published, and providing approved publishers with a monopoly in exchange for compliance was the tool. Having an unlicensed printing press was severely punished. Starting to sound familiar yet?

And yet we have been so thoroughly defeated in the copyfight that we have internalized the copyright lobby's talking points, like "copyright infringement == theft" and "there is no such thing as fair use", for instance when discussing the training of LLMs.

russel

I enjoyed this article, but even more I really enjoyed its title!

kornel

LLMs are killing GPL as a strategy for giving users computing freedom, but at the same time LLMs are also directly helping users have computing freedom. Now non-technical users are actually able to modify software themselves. Reverse Engineer Anything helps people liberate their hardware and replace proprietary software.