I'm kinda unclear on how this is any different than hundreds of other open source packages that debian ships that either require API keys (and agreement to an associated TOS) to function at all, or similar.
For example, there are numerous perl and python modules, shipped by debian, that require API keys to interact with services they are bindings for (AFAIK). There are numerous programs meant to automate various services, that directly interact with API's (even those that don't require keys), and those services all have a TOS.
So i'm having a lot of trouble understanding why this particular case is any different (except that Google seems willing to give distributions keys so users don't have to get them).
Past the fact that it got brought up because chromium is popular, can someone explain why the implications here are somehow different?
(disclaimer - i work for google, but this is a completely personal query)