> The AGPL denies recipients this freedom.
How does the AGPL deny recipients this freedom?
> The AGPL denies recipients this freedom.
How does the AGPL deny recipients this freedom?
This is the same demand the GPL always demanded of users, however the advent of cloud software has enabled a sort of loophole in the sense that making software based on GPL software available for users through a web interface was not regulated and thus imposed no demands for source redistribution (same for other distribution "through the cloud", for instance, some companies do this using VNC, RDP or Citrix. There's also custom protocols). If outlook used the Exim mail service, for instance, you would be able to get the source for that service from Microsoft.
It also closes the RPC loophole. If you build a GPL piece of software into another piece, connect them up using some sort of RPC interface, in GPLv2 it is somewhat unclear whether this constitutes redistribution (and therefore requires full source) or not. In AGPL/GPLv3, there is no doubt: it does require source to the whole thing.
Good luck replacing your linux kernel with something else. I mean FreeBSD is doable, but easy ... no.
Linus Torvalds never liked AGPL or GPLv3 and is quoted as saying that "it violates everything that v2 stood for".
Clearly, this server is a stand-alone product. However, it's also a piece of infrastructure that could be used by my other servers to do work for users.
Is the AGPL well defined for this case? Do I have to release the source for my entire product or just the PDF conversion server?
Perhaps I should also mention: Generating PDFs is a very, very small feature of my overall product. It's not the whole product. So, IMO this type of usage should be completely fair.
So, I cannot run the program as I wish for any purpose. I can run it for limited purposes: those where there is no network interaction, and those where the network interaction is rich enough to support offering source code.
I mean, it is probably reasonable, in the abstract, to have licenses that say "You may not modify this software internally and use it at all unless you make the changes public." Plenty of licenses have required that. Those licenses are non-free in the FSF sense, and they have rejected such licenses before.