Skip Navigation

Really interesting thoughts on whether the creators of free software really want their users to be free

werd.io I don't want my software to kill people

Open source licenses fall short of modern needs.

I don't want my software to kill people

I think we have to consider that the principles of the free software movement, revolutionary though they genuinely were, were also set in the same mindset that latterly saw its founder Richard Stallman spectacularly fall from grace. They are principles that deal in software development and licensing in strict isolation, outside of the social context of their use. They are code-centered, not human-centered.

(…)

It’s worth considering whose freedom we value. Do we value the freedom of the people who use software, or do we also value the freedom of the people the software is used on? While the latter group doesn’t always exist, when they do, how we consider them says a lot about us and our priorities.

20
20 comments
  • This is a conversation that needs to be happening, and not just around whether you are okay with the government using your work to kill people.

    Are you also okay with giant corporations that have enough money to develop their own tools use your volunteer labor to profit wildly and harm the public? (Also, private companies make tools to kill people as well. Just look at Palmer Luckey's Anduril, which produces military-grade drones and such. Or hell, any company that makes Tasers.)

    Because the story of Free Open Source Software is also the story of the biggest accidental transfer of wealth from the working class to the capital class in world history.

    Amazon Web Services wouldn't exist without Linux. Sure, they run their own flavor of Linux, but they've put in a bunch of their own proprietary bullshit and AWS is a fucking juggernaut. A big reason they're able to do this is because they use off-the-shelf Linux as a starting base and work from there. It cuts out a massive amount of labor to just lean on the labor of volunteers.

    Now, not all companies are like this, I'll admit. Valve pays people to improve Steam in Linux and has wildly benefited the WINe team.

    However, the vast majority of private companies lean on the labor of FOSS volunteers to make money without investing the same labor themselves.

    It's honestly kind of a fucking travesty.

    EDIT: Also, it's a bit ironic that RMS always claimed that his plans with GNU/Linux was to free people from proprietary gardens, yet FOSS has actually been one of the biggest creators of such gardens. I always had a soft spot for RMS, but he's wrong as much as he is right.

  • The goal of the copyleft movement (which overlaps heavily with the free software movement) is to carve out an intellectual commons that can't be re-enclosed. This commons is important for a number of reasons, including that it tends to be better for end-users of software in the sense that anti-features can't really gain a foothold. It does not automatically solve UX issues, nor does it stop people from using the knowledge of the commons to do bad things.

    Much of the strength of the intellectual commons is that it builds on itself, instead of having to re-invent the same things in a dozen or more different proprietary endeavors. If we were to start a "peace software" movement, it would be incompatible with the commons, due to the restrictions it imposes. Peace software can't build on copyleft software, and none of the commons can build on peace software. These sorts of things were considered, and compatibility was deemed more important than pushing more specific values. This isn't a matter of the FSF or OSI standing in the way, it's just that "peace software" would have to go it alone.

    Due to this dynamic, those that want to build "anticapitalist software" would be better served by using the GNU AGPL, rather than a license that restricts commercial use. The AGPL fixes the loophole that the GPL leaves open for network services, and should allow us to carve out a new noncommercial online ecosystem. It should even be used for non-network code, as that code may be repurposed or built upon by network services. I'm glad to see lemmy, kbin, and mastodon using it.

  • I've always felt the FSF has had no idea what they were doing. Therefore I do not always agree with or support 100% of what they do.

    I do feel that sometimes code should be able to carry reasonable restrictions. Just not sweeping restrictions.

    An example of a reasonable restriction would be a clause that prohibits commercialized use of free software without first obtaining permission from the project in question. Another reasonable restriction would be a clause that prohibits governmental use or use by military entities.

    An unreasonable restriction would be naming only specific companies that are not allowed to use the 'free' software. It would also be further considered unreasonable for rights to use 'free' software if it expires, goes away, or is revoked if you commit a specific crime, or fall under suspicion of committing said crime.

  • Isn't this treating the symptoms, not the cause? The real problem here seems to be that militaries and bad actors are killing people they obviously shouldn't, but it feels like the article just accepts that as something that "downstream users" do.

    I'm all for responsible software use, but I think the issue lies deeper than software licensing.

  • I was just trying (and failing) to imagine a distribution and development framework which was limited to those entities which agreed with a set of social parameters.

  • There is no good way to open source user research

    Users can easily give feedback to the developers by opening an issue on GitHub.

You've viewed 20 comments.