GPL 3.0 and web services

I've been pondering the impacts of the GNU General Public License and its impacts on web services lately, so here are some cool links I found that help describe the topic.

FSF legal counsel Eben Moglen has a great talk on FLOSS Weekly (podcast downloadable here), in which he talks about GPL 3.0's impact on web services, and if developers are required to disclose their logic when using remote data sources over the wire.

From another description (HTML version here):

Many companies use software that is subject to the GPL to provide services via the web. This has frustrated many at the FSF and in the open source community because it essentially means that a number of changes and enhancements to Linux and other programs subject to the GPL are created and used as web applications, but never shared with the community at large (which many believe is the very purpose of the GPL). There is a movement within the open source community and apparently in the FSF to close this loophole and require that the provision of web services be accompanied by changes to the source code allowing the provision of those services. There are multiple ways that this issue might be addressed in GPL 3.0, some of which might be acceptable and some not.

There's an equally intriguing post here on GPL 3.0 and SAAS:

In the second draft, this [software as a service] was addressed in section 7(b)4, which would've allowed licensors to optionally add a requirement to their code so that source would remain available even when the software was running as a network service. The language we proposed got the job done, but it was not an elegant solution. Proponents of the requirement...supported the goal but were unsatisfied with the execution.