The thing to keep in mind is that the changes that web companies make to free software are not usually for internal consumption. The changes are user-facing -- but the software is delivered via the web, rather than distributed to the users, and so the web company never triggers any requirement to make their changes available. The GPL does allow this, but it is not in the spirit of the GPL, and the Affero GPL was created to deal with this problem.
I agree that it's not in the spirit of the GPL, but they did explicitly not add in sections about that in the GPLv3. The v2 FAQ mentioned that they were considering adding in web-based applications, but the v3 FAQ says it's still okay, but if you're writing software and want to make it not okay, use the AGPL.
No, I'm addressing your prior claim that the Linux kernel is not open-source. The claim is false.
Also, companies that change the kernel, and then release their changed kernels, cannot do so without also releasing their source.
The claim is false, in whatever form it takes.
I did. Here is what you said:
> ...and untold millions of lines of changes to the Linux kernel are kept secret and are not at all available to other Linux users or even to Linux contributors. That is exactly the sort of the thing the GPL was meant to prevent.
It's false. Code that is modified and then never released is not what the GPL was meant to prevent.
But if they change the Linux kernel or an open-source server utility and put it on their cloud server, they don't. An unintended outcome, and one that makes the cloud different than what came before it.
So I concede that the cloud is different, and it does affect the idea of open-source.
The line is drawn if and when a client machine downloads an open-source app from the cloud. If that never happens, then there's no requirement to release source.