[jacooper]

> This viral effect requires that the complete corresponding source code of the product or service be released to the world under the AGPL license. This is triggered if the product or service can be accessed over a remote network interface, so it does not even require that the product or service is actually distributed..

This is the entire point. The goal is to stop the SAAS loophole.

[zmmmmm]

the toxic combination is (a) virality and (b) remote end user access triggering the GPL rights.

You could have one but not the other. We really need "LAGPL" to parallel LGPL, to make it clear that there is a clear and well defined way to stop the "remote access" part of AGPL from propagating accidentally into proprietary code.

[naasking]

In other words, to stop the process of people no longer owning their software and data and being subjected to someone else's decisions about whether a feature or service is important or should be deprecated.