I'd like to add another confirmation of this issue. I am the lead developer for a commercial application that has started receiving reports of Twitter sign-in failures over the last couple days and I was able to reliably reproduce the 15-second workaround before I came across this thread. I'm using the Hammock (.NET) library, against the api.twitter.com URLs over SSL, but I found the problem persists when I tried over HTTP and/or directed to the regular twitter.com URLs.
-- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
