3 ms·
The AGPL is designed to be impossible to comply with if any modifications are made to the program which are GPL-incompatible. That's the purpose of the AGPL.
by kazinator 6y ago
The AGPL is designed to be impossible to comply with if any modifications are made to the program which are GPL-incompatible.
That's the purpose of the AGPL.
It's a political tool for the GNU ideology whose intent it is to prevent the free software from being used for building services that are are also built on proprietary software.
Those situations cannot comply with the license, by design.
The AGPL is not about the user freedom at all. The user has no freedom because the user has no administrative access to alter the service software.
The software can do bad things that are harmful to the users, yet fully comply with the AGPL. The users have to accept that, or not use the service. The FSF wants it that if the users are going to be abused by an online service, at least this should be done with entirely free software, and that's where the AGPL comes in.
The AGPL (and copyright licensing in general) is completely the wrong tool for actually doing something to combating the social problem that people are becoming dependent on SaaS that is out of their control.
- Iolaum 6y agoThe user does have the freedom in forking the project and hosting it elsewhere. AGPL is actually about enforcing that the user has that option.
- kazinator 6y agoNo, you don't have that option for any site that matters. For instance, even if your bank uses nothing but AGPLed software, you can't just "git clone" their code and run your own fork of their online banking site. Or: even if Facebook were thoroughly AGPLed, running your own copy would be next to useless because only you and three other people would be there. Not having a copy of the exact software that services are running is not what is gnawing away at your freedom. It's completely the wrong problem to be focusing on.