4 ms·
The only thing that non-A GPL allows them to “hoard” that the AGPL does not are their own modifications. Your hard work is still available to the community. I
by sneak 7y ago
The only thing that non-A GPL allows them to “hoard” that the AGPL does not are their own modifications. Your hard work is still available to the community.
I don’t consider the AGPL to be free software. My freedoms to keep my own code to myself should not change based upon whether or not I am running a web server process on my machine or not.
I think it’s just generic anti-corporate/anti-business sentiment dressed up as egalitarianism. ASPs are a feature, not a bug.
- EGreg 7y agoWhy is anti-corporate sentiment not an example of egalitarianism? Seems to me that this is the paradox of intolerance... being intolerant of intolerance is a reasonable stance for otherwise tolerant people.
- cyphar 7y ago> The only thing that non-A GPL allows them to “hoard” that the AGPL does not are their own modifications. The point of the GPL family of licenses is not to solely make the author's "hard work available to the community". It's to ensure that any modifications which are later provided to other users must be licensed such that those users can make their own modifications. Private modifications are still permitted under the AGPL. In fact, the FSF explicitly states that licenses which disallow private modifications are not free software. > Your hard work is still available to the community. That'd also be true if you used CC-0 or made it public domain. That's not the point of using one of the GPL licences. > My freedoms to keep my own code to myself should not change based upon whether or not I am running a web server process on my machine or not. The AGPL doesn't say "if you run apached on your server you must release your code to everyone who asks for it". It says that people who use your software over a network must be given the source code. And in the context of SaaS and "online-only software" it's pretty clear why such a provision is necessary -- in the nightmare scenario, all software would be only accessible over the internet and you'd have no rights to the source code even if the code was GPL. You might not agree with this measure or the plausibility of such a nightmare scenario (and that's fine), but there is a clear ethical argument for it (and it is consistent with the history of the free software movement).
- kazinator 7y agoIn the AGPL version of the nightmare scenario, all software is still accessible only over the Internet. You have all the exact code, but running it yourself has no meaning because users and all their data will not migrate to your installation (which doesn't even have the capacity, but never mind that). The code does all sorts of nefarious things in plain view, but you're powerless to change the installations of that code. You can't stop using those services because life depends on it. Hundreds of millions of them continue to use the services, forcing you to do the same. Most of them don't understand the code or your objections to it. If the fictional character Don Quixote came up with a software license, it would be the AGPL. It's full of nice sentiment, but ineffective and self-defeating.
- cyphar 7y ago> You have all the exact code, but running it yourself has no meaning because users and all their data will not migrate to your installation. Free software licenses are mostly about your rights. You can host your own instance with your data. Stallman said on many occasions that it is not possible to exercise software freedom using a service hosted by someone else -- there is a fundamental clash between the freedoms of the users and the freedoms of the administrators. Both groups should be able to exercise their freedom, but unless the users are all administrators (of their own instances) there will always be a mismatch. > Hundreds of millions of them continue to use the services, forcing you to do the same. This is a fair point when it comes to social networks, because the AGPL doesn't require interoperability or the ability to federate (such terms would make little sense in a copyright license meant to be applied to all sorts of works). The real-world example would be the "fediverse" -- you could imagine a circumstance where all fediverse servers decide to block instances that don't implement $BadFeature. I would argue that in that nightmare scenario there really isn't a great solution even in theory. If you require interoperability, you've restricted the software freedoms of the other operators and now people can no longer block bad actors. But I would argue the AGPL does make the situation marginally better -- at least you could run your own (isolated) fediverse.
- kazinator 7y ago
- imtringued 7y agoSince when is free software about the freedoms of the owner of the software? You're trying to gaslight a new definition of free software that is going against the user of your software. When you look at the four software freedoms you will notice that not even once is the author of the software mentioned. Your definition of free software is 100% incompatible with the four software freedoms. >A program is “free software” if the program’s users have the four essential freedoms: >The freedom to run the program as you wish, for any purpose. >The freedom to study how the program works, and change it so it does your computing as you wish. Access to the source code is a precondition for this. >The freedom to redistribute copies so you can help your neighbor. >The freedom to distribute copies of your modified versions to others. By doing this you can give the whole community a chance to benefit from your changes. Access to the source code is a precondition for this. By running a modified GPL project on a web server without allowing access to the source code to users you are violating all 4 software freedoms at once. Users can't run the same software as you do. Users can't change the program because they have no access to the source code. They can't redistribute modified or unmodified copies. >My freedoms to keep my own code to myself should not change based upon whether or not I am running a web server process on my machine or not. The user's freedom should not change based upon whether or not the free software is running a web server process on a machine or not. This is the exact opposite of your argument and it is in line with the four software freedoms. Therefore your argument has nothing to do with free software.
- kazinator 7y ago> By running a modified GPL project on a web server without allowing access to the source code to users you are violating all 4 software freedoms at once. That is nonsense. Firstly, you can't violate freedoms, only exercise them or not. You're just running the program as you wish, for any purpose, exercising the first freedom. Since you modified it, you obviously had freedom to study how it works and change it how you wish. You haven't exercised your freedom to redistribute the program. > The user's freedom should not change based upon whether or not the free software is running a web server process on a machine or not. Yes, it should; the server is my private property. It is a social problem that people are allowing themselves to become locked to SaaS programs, and those programs are blackboxes whose behavior changes on a whim, and can be nefarious. That problem can't be solved by turning free software licenses into screwed-up non-free licenses. Even if you have the exact source code of some SaaS, that still doesn't help you because you don't control the installation. Users who are stuck with some system that they are pressured by others into using cannot just walk away from it just because they don't like what some piece of code is doing (in plain view, thanks to AGPL compliance).