Comments on: Apparently Twitter Can Break It’s Own Rules http://www.jessicahickok.com/archives/501 Jessica Hickok (a.k.a. @sugarcube) random rants and raves, type 1 diabetes, real estate and property management and everything in between. Tue, 27 Jul 2010 13:53:42 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Jessica Hickok http://www.jessicahickok.com/archives/501/comment-page-1#comment-353 Jessica Hickok Tue, 16 Jun 2009 13:55:26 +0000 http://www.jessicahickok.com/?p=501#comment-353 Thanks @greycloak! I think you probably summed up my problem in the last line of your comment. Thanks for your help! Thanks @greycloak! I think you probably summed up my problem in the last line of your comment. Thanks for your help!

]]> By: Aaron http://www.jessicahickok.com/archives/501/comment-page-1#comment-352 Aaron Tue, 16 Jun 2009 12:46:11 +0000 http://www.jessicahickok.com/?p=501#comment-352 Interesting that you're having that problem. I understood that Tweetdeck only refreshes set streams every X minutes. So no matter if you get 5 or 15 tweets, if the update every minute would only use up 60 requests within the hour. (This is all set in your Settings button under the Twitter API tab). I don't think the 100 limitation has anything to do with the number of incoming tweets. Now some other things that could possibly use that limit up? If you click on a username in Tweetdeck and their profile comes up in the application, that'll use a request up. However a bigger problem is if you have any other twitter clients running for your account. Say for instance if you have something running on your iphone and it's hitting twitter every minute, and so is tweetdeck. That's 120 per hour and then you go over your limit. The per hour limitation is based per account, not ip address. So anything that you may have logging in and accessing twitter with your account will affect it short of the website itself, or Friendfeed (which uses a different mechanism I believe). I hope you find the solution to your problem! I had this issue a while back, and my problem was I was running Tweetdeck and Twhirl both, and that was killing my request limit. Interesting that you’re having that problem. I understood that Tweetdeck only refreshes set streams every X minutes. So no matter if you get 5 or 15 tweets, if the update every minute would only use up 60 requests within the hour. (This is all set in your Settings button under the Twitter API tab). I don’t think the 100 limitation has anything to do with the number of incoming tweets.

Now some other things that could possibly use that limit up? If you click on a username in Tweetdeck and their profile comes up in the application, that’ll use a request up. However a bigger problem is if you have any other twitter clients running for your account. Say for instance if you have something running on your iphone and it’s hitting twitter every minute, and so is tweetdeck. That’s 120 per hour and then you go over your limit.

The per hour limitation is based per account, not ip address. So anything that you may have logging in and accessing twitter with your account will affect it short of the website itself, or Friendfeed (which uses a different mechanism I believe).

I hope you find the solution to your problem! I had this issue a while back, and my problem was I was running Tweetdeck and Twhirl both, and that was killing my request limit.

]]>