10 karma · joined October 26, 2011
It's not "some will say"; supplying object files for your code and source for the LGPL library is specifically listed as an option in the LGPL itself.
The threat is that a user logs in to googledrive.com and receives an authentication cookie tied to their Google account. Later, they view a malicious user page at googledrive.com/host/someevilpage, and a script on that page reads the authentication cookie and sends it to the attacker, who can now log in to googledrive.com as the victim.
That doesn't happen here because you don't actually log in to googledrive.com. The worst a malicious script could do is harvest data set by other scripts, and that's a drastically smaller (although still present) threat.
Here's a slightly outdated article that provides a good introduction to some of the legal issues: http://www.domainhandbook.com/property.html
(IANAL)