Thursday, February 11, 2010
In the recent past there have been a couple of changes regarding signing in to NewsRob/Google Reader. Judging by the feedback and a couple of thousands uninstalls this is a matter very close to the heart of many NewsRob users. So let me give you some background and a glimpse in the future.
Since very recently NewsRob/Google Reader sessions didn't expire for 3rd party apps. Now the expiration is two weeks. The introduction of this new policy was accompanied by an expiration of all sessions, so that you guys had to re-login.
Also recently another change in Google Reader broke the 3rd party apps. The Google Reader team very quickly rolled back the change, but many of you were affected. You needed to login again. Sorry for that.
There is an upside of the changes though, but more one that later.
On top of that NewsRob's login functionality wasn't as resilient as one would expect. As the sessions never timed out I felt that my time were better spent on other features. Well, live and learn ;-)
Meanwhile the current V3.5.3 handles expired sessions as it should have right from the beginning. This weekend I will release V3.6. This version will also handle CAPTCHAs and allow you to optionally save your password, so that NewsRob can auto-login you when the session expires.
Now to the upside I mentioned above. Some initial testing indicates that one of the recently deployed Google Reader changes now makes the Google Reader authorization compatible with the Android 2.0 Account/Authentication API.
That means, if everything works as expected, NewsRob 3.7 will not need to ask your for your Google account's password again. Instead there is an official way where your password is kept safe and you will only be asked to authorize NewsRob to access Google services using your account. Let me repeat that, the password itself will no longer to be disclosed to NewsRob.
You're probably as happy about that as I am ;-)
It's hard to say at the moment, but I expect NewsRob 3.7 to be out mid March.