• I can use Google webfonts on any project I like without registering.
    So why is this plugin insisting that I first get an API key from Google? This requires that I log into Google – from this moment on they log even more activity on my computer – which I don’t want!

    Yes, I have a Google webmaster account (which I rarely use), but neither a fixed IP, nor fixed address (as I’m a digital nomad) – Google only ever gets used with a login on IE, a browser I despise and never use for much else except maybe some testing. Development work and daily internet access happens through another browser, which I don’t want to see registered with Google. Full Stop. If I can’t do something simple w/o an API from Google then I’ll find another tool – basta! This was gone in less than 5 minutes.

Viewing 1 replies (of 1 total)
  • The reason why the author chose to add support for Google API auth is because it would be needed if you adapt the plugin into a theme options panel. It works great for doing things like previewing fonts selected and for a host of other reasons.

    Besides, if you can’t take five minutes to create a simple API key over at Google, then you are too lazy to appreciate the real benefits involved. Webbeetle, did you whine as much over at Twitter when they made you get an API key?

    Giving the developer of this plugin low marks because you are too lazy to appreciate the features you would get in return is a sad reflection on your inability to be fair, while reinforcing your obvious ignorance. BY all means, continue to grab everything you can for free like Googles font colections, while tuning your tin foil hat and dodging of black helicopters. Geesh!

Viewing 1 replies (of 1 total)
  • The topic ‘Lasted only minutes – why do I need a Google API?’ is closed to new replies.