The logical step here is what's alluded to at the end of the article: self hosting and doing things with FLOSS is impossible unless you're sufficiently one-of-u

The logical step here is what's alluded to at the end of the article: self hosting and doing things with FLOSS is impossible unless you're sufficiently one-of-us to get into the guts of software. We can only make this situation change when we recognise that including a wider audience is necessary, and for that we need to run things and support them for other people. Cooperatives are the way that strikes me as being the right one: giving everyone a share and a vote instead of the code itself. Nobody is going to vote to have the contents of their emails mined or their attention bought and sold. The legal infrastructure we would need for this is a Cooperative General License. The "four freedoms" in the GPL are born from academia and they show it. The "open" licenses are libertarianism and opportunistic IP laundering (from one failed startup to another) for the most part. A CGL could incorporate a restriction on use: personal or cooperative, but not corporate, not unless the form is the right kind. This is an old debate in tech but as the author says, one worth revisiting. We shouldn't be working for bastards, and certainly not giving them the gift of our incredibly valuable work.