A rough day at the office
Today, about an hour after releasing version 0.2 of Ostrich, Twitter announced they were experiencing difficulties with their API. More specifically, they had trouble with OAuth (the protocol needed to login).
Therefore, even though people were able to get their new version of Ostrich, if their session didn’t stick on the server, they couldn’t login anymore.
Before even thinking of looking at @twitterapi, I looked all over my app, made countless tests for 3+ hours thinking I did something wrong. Lesson learned. Always check the Twitter API’s account first and subscribe to them.
Sorry for this problem, if my app wouldn’t have been so new, regular users could’ve used it without any issues.
Please check back tomorrow. I’m hoping it’ll be fixed by now.
