▲ | gpm 5 days ago | |||||||||||||||||||||||||
My understanding of the theory that they're advocating is that the AGPL requires that when you modify AGPL software you modify it to provide an offer of its source. And that you can comply with that completely, run the software, and then have a proxy in front that strips that offer without violating the letter of the license. And if that theory works I think "substantial features" of the code could be directly (but for the indirection of that proxy) exposed. | ||||||||||||||||||||||||||
▲ | shakna 4 days ago | parent [-] | |||||||||||||||||||||||||
That would violate the license. > However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so. and > Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. "Convey" is the key word there. You _must_ convey the license. Stripping it out, is not conveying it. Why is it automatic? Because under the AGPL, the license is a part of the work itself. You cannot remove it or modify it, without breaking the license, and thus having no right to modify it in the first place. | ||||||||||||||||||||||||||
|