The problem starts with the old but highly important distinction of calling it "open source" instead of "libre software". "Open source" puts narrow emphasis on

The problem starts with the old but highly important distinction of calling it "open source" instead of "libre software". "Open source" puts narrow emphasis on the code itself, downplaying how that code is actually used, and the resulting abilities of its users. In the "open source" paradigm it makes perfect sense that you can study a piece of source code and even modify and run it locally, but then when you want to actually practically use that software, often to interact with other people, you're strongly incentivized to use the centrally controlled (aka proprietary) SaaS instance/copy/fork. This dynamic of stripping user agency and providing a canned product in its place is what allows businesses to view your project and your effort as a raw materials to be mined. "Libre software" keeps the emphasis on user freedom. Having the ability to modify and run the code is a necessary, but not sufficient part of that. SaaS is an attack on user freedom from shortcomings of the GPL3, just the way Tivoization was an attack on user freedom from (perceived and commonly held) shortcomings of the GPL2. By keeping the emphasis on user freedom, we can easily perceive these types of attacks as taking away user freedom. Whereas by focusing on one mechanism "open source" encourages identifying with operations of the attackers - eg that common fallacious refrain that you can always make your own centrally-controlled clone of a given site.