[twitter-dev] OAuth rate limit question
Hi, I have been reading about twitter api limits lately as a lot of my users are exhausting their 150reqs/h on a fairly regular basis. I came across the following post and noticed that if users login with OAuth, they are given 350 reqs/hr. http://groups.google.com/group/twitter-development-talk/msg/b09f2a3324728d89?pli=1 This was fair enough as you guys are trying to make twitter more secure (good work!); so we set about implementing OAuth on our client. We completed the implementation today, but fail to see the 350 reqs/ hr. We are still being limited by the 150 reqs/hr. I was just wondering whether there was something special we needed to do to get our req limits up to 350 for those users who login to our client with OAuth. Just to give you some background info, the client is a mobile web based client and all requests to twitter are made on our server on behalf of our users. If they are logged in with OAuth, the appropriate OAuth details are also handed through as part of the request. We know they are using OAuth as our 'updated via xxx' changes with using OAuth. Any help would be greatly appreciated! Thanks! Ben
[twitter-dev] Re: OAuth rate limit question
Awesome! thanks very much! We were still using twitter.com rather than the new api.twitter.com Thanks again! Cheers, Ben On Mar 3, 5:26 pm, Raffi Krikorian ra...@twitter.com wrote: are you connecting via oauth to api.twitter.com? if so, then please take a look at the rate limit headers and let me know what you see? On Tue, Mar 2, 2010 at 10:48 PM, Ben Novakovic bennovako...@gmail.comwrote: Hi, I have been reading about twitter api limits lately as a lot of my users are exhausting their 150reqs/h on a fairly regular basis. I came across the following post and noticed that if users login with OAuth, they are given 350 reqs/hr. http://groups.google.com/group/twitter-development-talk/msg/b09f2a332... This was fair enough as you guys are trying to make twitter more secure (good work!); so we set about implementing OAuth on our client. We completed the implementation today, but fail to see the 350 reqs/ hr. We are still being limited by the 150 reqs/hr. I was just wondering whether there was something special we needed to do to get our req limits up to 350 for those users who login to our client with OAuth. Just to give you some background info, the client is a mobile web based client and all requests to twitter are made on our server on behalf of our users. If they are logged in with OAuth, the appropriate OAuth details are also handed through as part of the request. We know they are using OAuth as our 'updated via xxx' changes with using OAuth. Any help would be greatly appreciated! Thanks! Ben -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Getting 500 responses from Twitter constantly
Hi, I run Mobile Tweete (http://m.tweete.net), and I've noticed within the last few hours that users keep getting 500 error response codes from the Twitter Api. I have a dev server running the exact same code on my machine here and I'm experiencing no such errors. I was just wondering whether Mobile Tweete's IP address has been blocked from the API for some reason? I would really love to get to the bottom of this ASAP! Thanks very much! The IP Tweete is running on is: 74.207.242.154. It also appears that 64.71.152.86 doesn't seem to work either. Cheers, Ben
[twitter-dev] Re: Getting 500 responses from Twitter constantly
since posting this - I've noticed other users on here have experienced the same problem. It only appears to happen to certain user accounts on home_timeline. Not sure what the issue is. I'm not over my rate limit because I can view replies/dms. Cheers, Ben On Dec 3, 11:37 am, Ben Novakovic bennovako...@gmail.com wrote: Hi, I run Mobile Tweete (http://m.tweete.net), and I've noticed within the last few hours that users keep getting 500 error response codes from the Twitter Api. I have a dev server running the exact same code on my machine here and I'm experiencing no such errors. I was just wondering whether Mobile Tweete's IP address has been blocked from the API for some reason? I would really love to get to the bottom of this ASAP! Thanks very much! The IP Tweete is running on is: 74.207.242.154. It also appears that 64.71.152.86 doesn't seem to work either. Cheers, Ben
[twitter-dev] Mobile Twitter has been blocked?
Hi, I was just wondering where I should post this, but it appears that Mobile Tweete (http://m.tweete.net) has been blocked. I worked up until about an hour ago, but now it appears as though no API requests are being processed. I can ping the twitter servers from the Tweete machine, but nothing else works. I have a staging server running the same trunk as the live box and that works fine (different machine/IP) so I can only assume I have been blocked. Any ideas on what I should do to avoid this. I realise that twitter is cracking down on 'threats' after the downtime about a month ago, but Mobile Tweete is a legitimate client that has been running for over a year now. Any help would be greatly appreciated. Kind Regards, Ben Novakovic -- Developer of Mobile Tweete
