>- Paragraph 4.b.1, which states that "You will keep your credentials >> confidential and make reasonable efforts to prevent and discourage other >> API Clients from using your credentials. Developer credentials may not be >> embedded in open source projects." prohibits the use of OAuth credentials >> in free software projects. As I wrote above (and earlier), Google >> tolerates (at the moment) that this specific point of their TOS is >> violated. But that doesn't mean that violating them is without legal >> risk.
Oof, fair enough. It does seem unfortunate that the official rules don't permit OSS projects; I wish there was a way for a user to create their own custom API key and they could just add that to their account. Honestly, I am fine with doing what KMail did (since that's what we did before). --Ken
