Comment Predicted long ago by GPLv3 (Score 1) 102
Way back then, when GPLv3 was veing written, this scenario was already had in consideration. We needed stronger copyleft for the online world of cloud services, and that was something Affero GPL and GPLv3 addressed.
But all the "business savvy" open source advocates made it hard to reach a consensus (they did not want the closure of the loopholes), instead they caused a bit of FUD chaos and then proceeded to have a strong impulse of new cloud oriented software that went all the way opposite the GPLv3 and in fact opened MORE loopholes, hence the strong investment into MIT, Apache 2, and other less strong free software licenses.
This way, they could make proprietary versions (and many companies went the proprietary relicensing bait and switch model of "open core") or turn software proprietary for all practical effects by having it used in cloud services (without the additional requisites addressed by GPLv3) without a "download me" recourse.
Nothing good ever comes from "there's a problem, instead of fixing it let's add more complexity".
And adding contracts to free software... IMHO, is an epitome of that.