Twitter API Bug?

Ever since @Jestertunes started messaging me on Twitter while in San Francisco for the 2008 Pride festivities, I’ve been addicted to the micro-blogging/social-networking behemoth.

It really took off when the iPhone apps for Twitter started popping up and even more so once a decent desktop application came to fruition in the form of Tweetdeck.

But recently I’ve been fucked over by the Twitter API limitations.  See, you are only allowed 100 pings to your Twitter account via third party applications such as Tweetdeck or Twitterriffic per hour.

Normally that’s OK for me.  I’d like more but 100 has been enough 95% of the time.

Every hour, on the hour, the API resets.  Except in the past week mine has not reset, which means I cannot update my Twitter, or view my friends’ updates.  Boo!  It also means my Brightkite to Twitter stream isn’t working.

Even with just a minute or two into the hour, I’ve exceeded my API limit.

I changed my password just to make sure there wasn’t another application through the internets hacking my account and loaded up Tweetdeck again.  Tweetdeck had my old password credentials but somehow updated all my replies and friends’ updates.  Doesn’t that require access to the Twitter API?

So I messaged @Twitter for their help and did my best to be light hearted.

Did I succeed?  I sure hope so.  I at least hope they can fix my account cause I’m dying getting all my friends’ updates via text message.  It’s making me crazy having my leg vibrate so much 😉

Reblog this post [with Zemanta]

3 thoughts on “Twitter API Bug?

  1. TweetDeck does that sometime. I can’t say whether or not other apps are better at not temporarily exceeding the Twitter API limit, but TweetDeck is still the best I’ve found for Twitter.

    (sometimes I just restart it and it forgets it ever told me I’d exceeded my limit.)

    Iron Fists last blog post…some assembly required

  2. What you’re seeing is the product of bad Twitter API design. I ran into this while building my latest website.

    Twitter has two methods of limiting your API access: a.) by your username and b.) by your IP address. Getting your replies is not something that’s private (something that needs your un/pw), so TweetDeck doesn’t even bother throwing your credentials in there. This way, it doesn’t count towards your account, it counts towards your computer.

    Now assuming that your rate limit is exceeded for your username, you wouldn’t have any hits counted towards your IP.

  3. thats great that you are talking about the twitter api,a good example of searching with the twitter api is on because you can search on twitter and google at the same time.

Leave a Reply

Your email address will not be published. Required fields are marked *