401s
A lot of people are seeing 401 authentication errors w/ Buzzbird right now… I’m not sure what the source is just yet, and I apologize profusely for the inconvenience! 
It’s not currently happening with the latest code in master, so it must be either something that was fixed between version 0.6 and the latest version, or something different about my credentials than everyone else’s (which isn’t as crazy as it sounds … developers get whitelisted so that the API limits don’t apply to us, so it’s possible that there’s some difference in API limiting that is causing the problem).
I’ll keep y’all posted – and sorry again if this bug is affecting you!
UPDATE 5-APR-2010 1:34 UTC: I’ve reproduced the problem in v0.6, and it is indeed something that I’ve fixed in the latest code. Mulling over whether I should press on and try to get 0.7 released tomorrow, or try to back-port a fix to 0.6.
I’m still waiting to hear back from @twitterapi to confirm that I’ve identified the problem. Thanks again for your patience!
This entry was posted on Monday, April 5th, 2010 at 20:08 and is filed under Blog. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.
One Response to “401s”
-
Mark Says:
Hi,
The 401′s started appearing when I upgraded my Ubuntu from 9.10 to 10.04 (beta) which has some security issues so I ‘assumed’ it was a Ubuntu issue. Not sure if this is a red herring but Buzzbird was rocking before I upgraded.
Mark
