I don't think it's just the wording of the license, though. It's really hard to envision every possibility and decide how the AGPL should handle it. E.g., are t

I don't think it's just the wording of the license, though. It's really hard to envision every possibility and decide how the AGPL should handle it. E.g., are they really going to add something as specific as "If a cloud service provider hosts its own code along with user code that includes AGPL code, the cloud service provider is not bound by the AGPL and the user does not need to include the provider's bundled code when they release the source code in compliance with the AGPL."? Plus, if you treat the cloud service provider's code separately from the user's code, there is a pretty strong danger of opening loopholes that defeat the entire purpose of the AGPL. It's not clear that people releasing code under the AGPL would even want the AGPL to be interpreted that way.