Twhirl log-in = Authentication Failed! (Status:304)
The more people who ask this question, the more it gets noticed.
The best answer from the company
-
Hi all, sorry that I didn't respond sooner. :( Needless to say it got a little crazy there for a while, but thats not a good enough excuse not to make time to hop in here and answer your questions.
It *seems* like Twhirl's inability to login was directly related to API issues stemming from Twitters caching issues today. And, yes, we do need to implement a better way to inform you when Twhirl issues are based on a twitter failure rather than any user or client error. (i.e. "twitter is broke, not us")
Thank you for helping one another out in our absence.
I’m making a mental note to hop in here no matter how crazy it gets on the "front lines"
The company says
this answers the question
-
Inappropriate?Is this related to twitter's caching service going down?
http://blog.twitter.com/2008/05/what-...
maybe you need some way of updating your users when theres a problem like this. Rather than us all searching help topics.
I’m frustrated
-
Inappropriate?Same issue for me, checked my twitter a/c and that's functioning fine. Twhirl V 0.81, Vista Ultimate.
-
Inappropriate?Glad to know its not unique, and I am amazed at how quickly people joined this topic and replied. I guess this is the Twitter community, afterall...
-
Inappropriate?Just saw a message on Twitter from Twhirl saying to restart, but it's still not working...
I’m frustrated
-
Inappropriate?I have the same issue, Twhirl 0.8.1 on Mac OS X 10.5.2
I also have tried restarting the client multiple times so far.
I’m frustrated
-
Inappropriate?Twhirl 0.8.1 on Windows XP SP3 here. Restarted client a number of times. Twitter account works fine through web.
I’m frustrated
-
Inappropriate?*Had* the same issue, working ok now. Lets cross our fingers that it stays up!
I’m undecided
-
Inappropriate?Hi all, sorry that I didn't respond sooner. :( Needless to say it got a little crazy there for a while, but thats not a good enough excuse not to make time to hop in here and answer your questions.
It *seems* like Twhirl's inability to login was directly related to API issues stemming from Twitters caching issues today. And, yes, we do need to implement a better way to inform you when Twhirl issues are based on a twitter failure rather than any user or client error. (i.e. "twitter is broke, not us")
Thank you for helping one another out in our absence.
I’m making a mental note to hop in here no matter how crazy it gets on the "front lines"
The company says
this answers the question
-
Inappropriate?Still no luck for me signing in. Sorry, could not log you in to twitter
with that username and password.
Could not authenticate you.
I’m frustrated
Loading Profile...












EMPLOYEE
