Privacy Questions/Concerns Rated 5 out of 5 stars
I have no issues with the performance of the add-on itself, it works perfectly and does exactly what it's supposed to do, however, I'm always leery about granting apps access to my google account so I was wondering what granting your app access encompasses. What exactly am I granting your app (you?) access to in my google account? Do you have access to this information? And if you do, how is our data being stored and protected?
(By no means am I accusing you or suggesting that you have bad intentions or anything, like I said, I'm just extremely cautious and overprotective of my google account so I was just curious to know some further information for my own piece of mind).
Just shortening URLs
You're right to be careful. I'm doing what it says on the tin, but you can check. You don't need to take my word for it.
To be sure, you can right-click the download button, save the add-on, rename it to ZIP, unzip it, then look at the source.
In resources/goo_gl_lite/module.jsm , you will see that I'm only requesting the https://www.googleapis.com/auth/urlshortener scope, which is pretty self-explanatory. It means the add-on can only manage shortened URLs. In practice, it only adds them.
Also, when you connect your account, Google will say:
goo.gl lite is requesting permission to:
Manage your goo.gl short URLs
I (the author) don't have any access. The token (basically a login cookie) is stored on your machine.
Not Working Since 1.8.1 Upgrade Rated 4 out of 5 stars
I had received that captcha error for the first time earlier today, but then once I logged into goo.gl everything was back to working as normal. However, since upgrading to the latest version, 1.8.1, I can still create a goo.gl url by right-clicking on websites, but they now no longer show up on my goo.gl page (and yes, I'm logged in and allow cookies).
Can I downgrade to the previous version?
How to downgrade
Yes, follow the instructions at http://www.ghacks.net/2011/12/18/how-to-downgrade-firefox-add-ons/. However, if you do so, please check back. I will post an update when I have authentication working with the new API.