4 ms·
Oh phooey, all this does is extend GPL rights to users who are running the code over a network rather than their own machine. If you don't like the GPL then yo
by gumby 6y ago
Oh phooey, all this does is extend GPL rights to users who are running the code over a network rather than their own machine.
If you don't like the GPL then you won't like this. OK, I generally disagree, but reasonable people can disagree.
If you do like the GPL this merely fixes an important corner case.
And if you are someone who pretends to like the GPL but hides their work behind a network connection: just grow up and admit you don't like the GPL. Don't lie for PR purposes.
- sneak 6y agoI really like the GPL and I really care about software freedom. I think the AGPL is nonfree. It attempts to redefine the provision of a service as the same as the provision of software. They are not the same thing at all. I believe that software freedom includes the right to keep my own local modifications private, if I'm not distributing the software (but only using that software locally to provide a network service).
- bombcar 6y agoI think at the root of the issue is that "Freedom 0" and being against "SaaSS" as rms calls it, are incompatible. See https://www.gnu.org/philosophy/who-does-that-server-really-serve.en.html https://www.gnu.org/philosophy/who-does-that-server-really-s... The AGPL (and I would argue that even the GPLv3) attempt to restrict Freedom 0 to prevent "evil companies" (or if you want to word it differently "dumb customers") from foot gunning themselves. The AGPL and the GPLv3 would not be NEEDED if customers refused to use those products - but since the vast majority of people don't care about software freedom, the AGPL and GPLv3 try to prevent it - by restricting Freedom 0. Perhaps slightly, perhaps it's a good trade-off, but it's still a restriction.
- sneak 6y agoThis is a very clear and succinct way of putting it, and I think you're absolutely correct in your analysis. I care a lot more about Freedom 0 than trying to "fix" the legitimate choices of customers and vendors.
- aflag 6y agoWhat about the users of the software you provide via the network, don’t they have the freedom to run, modify and study the software they are using? If you stop providing the service, don’t they have the freedom to run it somewhere else and keep using it as they did? When it comes to remote use of software, the freedom to copy and run is even more critical. Microsoft can’t prevent me from running windows 95, but google can sure prevent me from using gmail in future.
- sneak 6y agoAssuming I'm an "evil ASP" in this model: I am not providing software via the network. I'm providing JSON (or protobuf or whatever), in response to questions. Distributing software and providing a service via an API are not in any way the same thing. One is a noun and one is a verb!
- aflag 6y agoSure, they are not the same thing. I’m just pointing out that the freedom in free software is all about users having the freedom to do with the software they use as they please, not about the freedom of people hiding parts of how the software works. You are not evil, you’re just restricting your user’s freedom, which is neither wrong nor a crime.
- sneak 6y agoThe users have no rights to software that hasn't been provided to them. There's no "freedom" involved. Imagine a situation where I provide a human based service: someone comes to me and asks me to add two numbers together. I return the next day and tell them the sum. They are not entitled to know whether I used pen and paper, computer, software, whatever. That's private information, and it's my freedom not to share information that's not relevant to that business transaction. It actually has nothing to do with software. I theorize that the AGPL isn't actually enforceable as a result. I don't know of any actual AGPL enforcements against service providers.
- 6y ago
- pritambaral 6y ago> ... keep my own local modifications private, if I'm not distributing the software (but only using that software locally to provide a network service). Nuance: The AGPL allows you to keep your modifications private _if you're not distributing the software_. It simply considers over-the-network usage as "distribution". That is how it defines it, in the legal text. This makes sense in many cases, where software is written primarily or solely for the purposes of providing network services. Authors of such software need a way to define network access as "distribution", and they have the AGPL for such software. > I believe that software freedom includes the right to ... Similarly, the permissive-licenses camp also believes software freedom includes the right to some things that the copyleft camp does not provide. Fundamentally, it comes down to a tradeoff: between the rights of a developer and the rights of an end-user. The permissive-licenses spirit places the former over the latter, and the copyleft spirit does it the other way. But in both cases, software freedom is maintained, even if for at most one type of persons. Sadly, it is logically impossible to maintain software freedom for both developers and end-users.
- bombcar 6y agoHow precisely is "over the network" defined? If I browse a website that has a Varnish cache in front of Apache running Wordpress am I using all three? Just one? If I upload a file via FTP and later a cron-job runs and processes that file via a software package and I later download the result did I interact with the "software package" in such a way as to count as over-the-network?
- aflag 6y agoI don’t think there are clear cut answers. It has to be tried in court. The desire of the creator is sort of obvious, the discussion will be whether the creator can set that as a condition to use their IP or not. EULAs are a thing, so I wouldn’t dismiss the license so easily.
- friend-monoid 6y agoDid you read the OSL version of the same statement? It’s kind of beautiful in comparison. I think its an amazingly insightsful article. Like “clean code”, but it’s a license.
- MaxBarraclough 6y ago> If you do like the GPL this merely fixes an important corner case. Disagree. As the article states, it's importantly different from the GPL, even under the FSF's own philosophy. As others have already pointed out, it could be said to infringe on Freedom Zero, The freedom to run the program as you wish, for any purpose. [0] At the risk of just writing a far inferior rehash of the article: under the GPL, you can take code, modify it (Freedom 1), and run that code on your machine under whatever terms you want, e.g. as an Internet-enabled service. You are not obligated to publish the resulting source code, provided you also refrain from publishing the binaries corresponding to the modified source. With the AGPL, that's no longer the case. One could argue it's just a matter of degree, as the GPL imposes rules on linking against non-GPL code, but I think the difference is still an important one. Following copyleft, the FSF understanding of being free to do something typically doesn't preclude free but with an obligation to release your source under a Free Software licence. They do seem to have a limit though. The FSF consider the Watcom 1.0 licence to be non-Free because of its far-reaching source-publication requirements, which can apply even to private use. [1] The AGPL does something similar, except it only applies when your deployment is publicly accessible. (This is, of course, the whole point.) Quite apart from all that, this isn't the first time I've read of technical legal issues with the way the licence is written, far exceeding those of the GPLv3. [0] https://www.gnu.org/philosophy/free-sw.en.html https://www.gnu.org/philosophy/free-sw.en.html [1] https://directory.fsf.org/wiki/License:Watcom-1.0 https://directory.fsf.org/wiki/License:Watcom-1.0
- mr_toad 6y ago> and run that code on your machine under whatever terms you want As long as you don’t distribute it.