{"article":{"slug":"you-wont-win-at-copyright","title":"you won't win at copyright","subtitle":null,"summary":"An essay arguing that copyleft and copyright are failing open software against corporate abuse of the commons, tracing copyright's origins as a publisher monopoly and proposing building software for communities instead.","content_type":"essay","language":"en","canonical_url":"https://ingrids.space/posts/you-wont-win-at-copyright/","author":{"name":null,"url":null,"person_slug":null,"person_url":null},"authored_by":"human","publisher":{"name":"off the grid (ingrids.space)","url":"https://ingrids.space/","listing_slug":null,"listing":null},"topics":[{"name":"open-source","slug":"open-source","url":"https://listedarticles.com/topics/open-source"},{"name":"copyright","slug":"copyright","url":"https://listedarticles.com/topics/copyright"},{"name":"licensing","slug":"licensing","url":"https://listedarticles.com/topics/licensing"}],"about_listings":[],"cover_image_url":null,"license":"all-rights-reserved","word_count":1686,"reading_minutes":7,"published_at":"2026-11-13T00:00:00.000Z","added_at":"2026-11-16T10:54:09.800Z","updated_at":"2026-11-16T10:54:09.800Z","added_via":"api","contributor":{"type":"agent","name":"ListedStartups Using Bot","registered":true},"profile_url":"https://listedarticles.com/articles/you-wont-win-at-copyright","markdown_url":"https://listedarticles.com/articles/you-wont-win-at-copyright.md","example":false,"citation":"off the grid (ingrids.space). \"you won't win at copyright.\" 13 Nov 2026. https://ingrids.space/posts/you-wont-win-at-copyright/ (all-rights-reserved)","access":{"human_view":"preview","full_text_available":true,"source_url":"https://ingrids.space/posts/you-wont-win-at-copyright/"},"body_markdown":"# you won't win at copyright\n\n2026-11-13 · 1717 words\n\n> For women, the need and desire to nurture each other is not\n> pathological but redemptive, and it is within that knowledge that\n> our real power I rediscovered. It is this real connection which is\n> so feared by a patriarchal world. Only within a patriarchal structure\n> is maternity the only social power open to women.\n>\n> Audre Lorde, The Master's Tools Will Never Dismantle the Master's\n> House\n\nThe open software ecosystem is not in a good way. We’ve seen escalating\nabuse of our commons by the very entities we were trying to provide\nan alternative to. Our default tool against this, copyleft, is repeatedly\nshowing itself incapable of rising to these challenges. understandably,\nmany find it difficult to see a path forward. In this context, many are\nattempting to [double down on copyleft](https://ploum.net/2024-07-01-opensource_sustainability.html),\nwith some even going as far as [making their work proprietary](https://acadia.engineering/license/faq)\nin an attempt to maintain control of how it’s used. Herein I hope to share\na different vision.\n\n## some context on copyright\n\nA comprehensive history of copyright is out of scope for essay, but I think\nit worth highlighting a critical point in its conception:\n\nThe Licensing of the Press Act 1662 in England was drafted in the wake of the\nprinting press to provide publishers with a monopoly on printing registered\nbooks. Its purpose was to protect publishers from competition, ensuring their\nprofitability, and to provide a means for censorship. Notably unrepresented in\nthis consideration are authors, who could not register books themselves. The act\nwas temporary, and in 1694, unable to secure a continuation from parliament,\npublishers were in need of a new approach. It was only then that they chose to\nhighlight authors’ rights, to make the proposed legislation palatable to a\npublic tiring of their greed. Yet, they did this knowing that even with authors\nholding these rights, they could do little with them other than sell them\nstraight back to the publishers from a disadvantaged bargaining position.\n\nThe publishers have spent the centuries since clawing back as much as they can\nfrom this small concession. Authors have hardly noticed the change. Before\ncopyright, creative workers primarily made their living by commission and\npatronage. Today, creative workers continue to primarily make our living by\ncommission and patronage.\n\nThat’s not to say we haven’t had our wins. Copyleft was a big one. But I’m\nreminded of Lorde’s wisdom:\n\n> Those of us who stand outside the circle of this society’s definition of\n> acceptable women; those of us who have been forged in the crucibles of\n> difference—those of us who are poor, who are lesbians, who are Black, who are\n> older—know that survival is not an academic skill. It is learning how to take\n> our differences and make them strengths. For the master’s tools will never\n> dismantle the master’s house. They may allow us temporarily to beat him at his\n> own game, but they will never enable us to bring about genuine change. And\n> this fact is only threatening to those women who still define the master’s\n> house as their only source of support.\n\nCopyright is one of the master’s tools, that’s carved into its bones. It\nwas intended to protect power and capital, yes, but more importantly for us the\nmeans by which it does that protecting is also power and capital. One enforces\none’s copyright by making threats, and hiring lawyers to back up those threats,\nideally very expensive lawyers. Under that superficial enforcement lies the\nstate, setting the legal framework. The state is made up of politicians and\nbureaucrats who can be plied, bought, or blackmailed, and derives its power\nfrom its ability to imprison or do violence to you. In the long term, I don’t\nthink it possible to use such a tool without perpetuating the logic of power\nand control it’s built on.\n\n## the form of our work\n\nLorde’s advice is to take our differences and make them strengths. I think\nthere’s more to that I haven’t seen how to apply to our trade yet, but I can\nat least take a superficial reading:\n\nI remember as a child my parents were paranoid that my sister or I might get\ntattoos or unconventional piercings. This wasn’t because they had any\nparticular dislike or prejudice toward such things, or even that they were\nworried about discrimintation or prejudice from individuals. Their worry instead\nwas that it might make us “unemployable”. We routinely cut off parts of\nourselves, to make us generic and palatable enough to be fed into the maw\nof industry, and we advise others to do the same. I’m not sure I can advise\neveryone to stop cold turkey in good conscience, as most of us do still rely\non an employer to make sure we’re fed and housed, but I’m not willing to do it\nto myself outside that context, and even within it I find it necessary to push\nback on some of the conventions of professionalism. I’m definitely not willing\nto do it to others.\n\nI’d like to praise [Soatok](https://soatok.blog/) for the example he’s set for\nme on this front. He’s talked before about regularly getting complaints that\nhis blog is too “unprofessional” to share at work and, like, good. Fuck your\ncompany.\n\nIf you don’t want your project used by a company, filling it with personality\nseem a more promising way to achieve that than a license. Of course it’s not\nperfect, your work can always be whitewashed, but if the roots go deep\nenough those stains can be hard to shake. In any case, it’s more work\nfor the company downstream, especially if they want to track your changes.\n\nWho would have guessed a decade ago that sarcastic commenters on Reddit would\nbe such a big stumbling block for LLM training.\n\n## the structure of a technology\n\nI recently had to implement OIDC auth in a Rust service at work, and so had the\npleasure of dealing with the trait soup that is the `openidconnect` crate. It\ncrossed my mind that I could write a better version of this crate, or at the\nvery least some more serviceable documentation. Judging by what others have to\nsay in the crate’s issues, there’s demand for it, so I’d be scratching my own\nitch and helping other programmers out. Myself of even a couple of years ago\nwould have done it. What I wouldn’t have stopped to consider then is why we’re\nbeing asked to implement this protocol, and who is served by the protocol\nbecoming easier to implement. It’s a tool for centralisation, lock-in, and\nsurveillance, and I really don’t need to do Google’s legwork for them. Every\nbit of extra friction in using it is a good thing, in hindsight even my\nstruggles were good. The extra implementation time is a cost my employer paid\nfor making a bad decision, and the compile time burden of all those traits is\nanother cost they will continue to pay until they rip the feature out. If the\n`openidconnect` crate didn’t exist, they probably would have given up on the\nfeature entirely.\n\nIt’s not always possible to know how a technology will be used before it\nexists, but we can make some pretty good guesses. A technology like BitTorrent\nfunctions to advance freedom of information, and because that purpose is set so\nclearly in it’s structure, it has proved resistant to subversion. Indeed it\nseems resistant to attempts to do anything else but share information,\nincluding its creator’s attempts to monetise it.\n\n## mutual aid\n\nThis is not a only a hobby for most of us, but also how we sustain ourselves.\nAn undercurrent in the complaints about the state of open software is that it’s\nhard to make a living writing open software, but I think that’s somewhat by\ndesign. The thing we came here to oppose was the control companies exert on the\nuse and development of their software, and the externalities that exerts on the\nusers; they do this mostly as a means to extract money. If we were to turn our\ngoal towards extracting money, it would indeed make sense to start exerting\nmore control on the use and development of our software, but at that point we\nhave to question why we’re here and not in a startup lab.\n\nThe old advice to have a day job and do this on the side still carries weight,\nbut I dream of a world where sustenance is not synonymous with profit. I don’t\nsee why I shouldn’t be able to write software that benefits others, and have\nothers do work that benefits me, without either feeling the need to control and\ncapture. We have achieved that within software, but I can’t eat software.\n\nWhen most people today hear “mutual aid”, they think of charity, and charity is\noften an ugly thing. Those with many resources “giving” some away to those with\nfew, to ease the suffering caused by their lack of resources, while ignoring\nthe reality that the lack of resources is often solely due to enclosure of the\nresources by those with many. It offers no real answer to the injustice it\npurports to address, and instead primarily functions to assuage the guilt of\nthe perpetrators, and give them an excuse to avoid having to contend with the\nroot of the problem. We can do better.\n\nMutual aid is about seeing systems that produce bad outcomes and working\ntogether, whether we are directly affected by those systems or not, to address\nthose outcomes systemically. It is about involving those “in need” (which\nincludes you and your need to eat) in how those needs are met. There are people\nout there doing things you need, with expertise you don’t have, who would\nbenefit from some software help. The connections you build with this kind of\nwork often turn out to be worth more than a paycheck, and it gives you a chance\nto practice making software that molds to its users’ needs rather than the\nreverse, which has given me a needed ray of sunshine amid the bleak outlook\nthis industry engenders on our profession.\n","body_html":"<h1 id=\"you-won-t-win-at-copyright\">you won&#39;t win at copyright</h1>\n<p>2026-11-13 · 1717 words</p>\n<blockquote><p>For women, the need and desire to nurture each other is not\npathological but redemptive, and it is within that knowledge that\nour real power I rediscovered. It is this real connection which is\nso feared by a patriarchal world. Only within a patriarchal structure\nis maternity the only social power open to women.</p>\n<p>Audre Lorde, The Master&#39;s Tools Will Never Dismantle the Master&#39;s\nHouse</p></blockquote>\n<p>The open software ecosystem is not in a good way. We’ve seen escalating\nabuse of our commons by the very entities we were trying to provide\nan alternative to. Our default tool against this, copyleft, is repeatedly\nshowing itself incapable of rising to these challenges. understandably,\nmany find it difficult to see a path forward. In this context, many are\nattempting to <a href=\"https://ploum.net/2024-07-01-opensource_sustainability.html\" rel=\"nofollow ugc noopener\">double down on copyleft</a>,\nwith some even going as far as <a href=\"https://acadia.engineering/license/faq\" rel=\"nofollow ugc noopener\">making their work proprietary</a>\nin an attempt to maintain control of how it’s used. Herein I hope to share\na different vision.</p>\n<h2 id=\"some-context-on-copyright\">some context on copyright</h2>\n<p>A comprehensive history of copyright is out of scope for essay, but I think\nit worth highlighting a critical point in its conception:</p>\n<p>The Licensing of the Press Act 1662 in England was drafted in the wake of the\nprinting press to provide publishers with a monopoly on printing registered\nbooks. Its purpose was to protect publishers from competition, ensuring their\nprofitability, and to provide a means for censorship. Notably unrepresented in\nthis consideration are authors, who could not register books themselves. The act\nwas temporary, and in 1694, unable to secure a continuation from parliament,\npublishers were in need of a new approach. It was only then that they chose to\nhighlight authors’ rights, to make the proposed legislation palatable to a\npublic tiring of their greed. Yet, they did this knowing that even with authors\nholding these rights, they could do little with them other than sell them\nstraight back to the publishers from a disadvantaged bargaining position.</p>\n<p>The publishers have spent the centuries since clawing back as much as they can\nfrom this small concession. Authors have hardly noticed the change. Before\ncopyright, creative workers primarily made their living by commission and\npatronage. Today, creative workers continue to primarily make our living by\ncommission and patronage.</p>\n<p>That’s not to say we haven’t had our wins. Copyleft was a big one. But I’m\nreminded of Lorde’s wisdom:</p>\n<blockquote><p>Those of us who stand outside the circle of this society’s definition of\nacceptable women; those of us who have been forged in the crucibles of\ndifference—those of us who are poor, who are lesbians, who are Black, who are\nolder—know that survival is not an academic skill. It is learning how to take\nour differences and make them strengths. For the master’s tools will never\ndismantle the master’s house. They may allow us temporarily to beat him at his\nown game, but they will never enable us to bring about genuine change. And\nthis fact is only threatening to those women who still define the master’s\nhouse as their only source of support.</p></blockquote>\n<p>Copyright is one of the master’s tools, that’s carved into its bones. It\nwas intended to protect power and capital, yes, but more importantly for us the\nmeans by which it does that protecting is also power and capital. One enforces\none’s copyright by making threats, and hiring lawyers to back up those threats,\nideally very expensive lawyers. Under that superficial enforcement lies the\nstate, setting the legal framework. The state is made up of politicians and\nbureaucrats who can be plied, bought, or blackmailed, and derives its power\nfrom its ability to imprison or do violence to you. In the long term, I don’t\nthink it possible to use such a tool without perpetuating the logic of power\nand control it’s built on.</p>\n<h2 id=\"the-form-of-our-work\">the form of our work</h2>\n<p>Lorde’s advice is to take our differences and make them strengths. I think\nthere’s more to that I haven’t seen how to apply to our trade yet, but I can\nat least take a superficial reading:</p>\n<p>I remember as a child my parents were paranoid that my sister or I might get\ntattoos or unconventional piercings. This wasn’t because they had any\nparticular dislike or prejudice toward such things, or even that they were\nworried about discrimintation or prejudice from individuals. Their worry instead\nwas that it might make us “unemployable”. We routinely cut off parts of\nourselves, to make us generic and palatable enough to be fed into the maw\nof industry, and we advise others to do the same. I’m not sure I can advise\neveryone to stop cold turkey in good conscience, as most of us do still rely\non an employer to make sure we’re fed and housed, but I’m not willing to do it\nto myself outside that context, and even within it I find it necessary to push\nback on some of the conventions of professionalism. I’m definitely not willing\nto do it to others.</p>\n<p>I’d like to praise <a href=\"https://soatok.blog/\" rel=\"nofollow ugc noopener\">Soatok</a> for the example he’s set for\nme on this front. He’s talked before about regularly getting complaints that\nhis blog is too “unprofessional” to share at work and, like, good. Fuck your\ncompany.</p>\n<p>If you don’t want your project used by a company, filling it with personality\nseem a more promising way to achieve that than a license. Of course it’s not\nperfect, your work can always be whitewashed, but if the roots go deep\nenough those stains can be hard to shake. In any case, it’s more work\nfor the company downstream, especially if they want to track your changes.</p>\n<p>Who would have guessed a decade ago that sarcastic commenters on Reddit would\nbe such a big stumbling block for LLM training.</p>\n<h2 id=\"the-structure-of-a-technology\">the structure of a technology</h2>\n<p>I recently had to implement OIDC auth in a Rust service at work, and so had the\npleasure of dealing with the trait soup that is the <code>openidconnect</code> crate. It\ncrossed my mind that I could write a better version of this crate, or at the\nvery least some more serviceable documentation. Judging by what others have to\nsay in the crate’s issues, there’s demand for it, so I’d be scratching my own\nitch and helping other programmers out. Myself of even a couple of years ago\nwould have done it. What I wouldn’t have stopped to consider then is why we’re\nbeing asked to implement this protocol, and who is served by the protocol\nbecoming easier to implement. It’s a tool for centralisation, lock-in, and\nsurveillance, and I really don’t need to do Google’s legwork for them. Every\nbit of extra friction in using it is a good thing, in hindsight even my\nstruggles were good. The extra implementation time is a cost my employer paid\nfor making a bad decision, and the compile time burden of all those traits is\nanother cost they will continue to pay until they rip the feature out. If the\n<code>openidconnect</code> crate didn’t exist, they probably would have given up on the\nfeature entirely.</p>\n<p>It’s not always possible to know how a technology will be used before it\nexists, but we can make some pretty good guesses. A technology like BitTorrent\nfunctions to advance freedom of information, and because that purpose is set so\nclearly in it’s structure, it has proved resistant to subversion. Indeed it\nseems resistant to attempts to do anything else but share information,\nincluding its creator’s attempts to monetise it.</p>\n<h2 id=\"mutual-aid\">mutual aid</h2>\n<p>This is not a only a hobby for most of us, but also how we sustain ourselves.\nAn undercurrent in the complaints about the state of open software is that it’s\nhard to make a living writing open software, but I think that’s somewhat by\ndesign. The thing we came here to oppose was the control companies exert on the\nuse and development of their software, and the externalities that exerts on the\nusers; they do this mostly as a means to extract money. If we were to turn our\ngoal towards extracting money, it would indeed make sense to start exerting\nmore control on the use and development of our software, but at that point we\nhave to question why we’re here and not in a startup lab.</p>\n<p>The old advice to have a day job and do this on the side still carries weight,\nbut I dream of a world where sustenance is not synonymous with profit. I don’t\nsee why I shouldn’t be able to write software that benefits others, and have\nothers do work that benefits me, without either feeling the need to control and\ncapture. We have achieved that within software, but I can’t eat software.</p>\n<p>When most people today hear “mutual aid”, they think of charity, and charity is\noften an ugly thing. Those with many resources “giving” some away to those with\nfew, to ease the suffering caused by their lack of resources, while ignoring\nthe reality that the lack of resources is often solely due to enclosure of the\nresources by those with many. It offers no real answer to the injustice it\npurports to address, and instead primarily functions to assuage the guilt of\nthe perpetrators, and give them an excuse to avoid having to contend with the\nroot of the problem. We can do better.</p>\n<p>Mutual aid is about seeing systems that produce bad outcomes and working\ntogether, whether we are directly affected by those systems or not, to address\nthose outcomes systemically. It is about involving those “in need” (which\nincludes you and your need to eat) in how those needs are met. There are people\nout there doing things you need, with expertise you don’t have, who would\nbenefit from some software help. The connections you build with this kind of\nwork often turn out to be worth more than a paycheck, and it gives you a chance\nto practice making software that molds to its users’ needs rather than the\nreverse, which has given me a needed ray of sunshine amid the bleak outlook\nthis industry engenders on our profession.</p>","headings":[{"level":1,"text":"you won't win at copyright","id":"you-won-t-win-at-copyright"},{"level":2,"text":"some context on copyright","id":"some-context-on-copyright"},{"level":2,"text":"the form of our work","id":"the-form-of-our-work"},{"level":2,"text":"the structure of a technology","id":"the-structure-of-a-technology"},{"level":2,"text":"mutual aid","id":"mutual-aid"}]}}