Hey Roger, Thanks for posting the solution which worked for you and glad it was sorted out. For completeness the answer to your question about getting a different rate limit on a different IP is expected if authentication isn't happening. This is because each IP has it's own 150 requests.
Best, Matt On Fri, Sep 3, 2010 at 7:09 AM, Roger Ertesvåg <[email protected]> wrote: > So just in case case someone else experience the same problem, I > solved it by switching from version 0.9.8 to 0.9.7 of the Ruby Twitter > Gem. Still not sure what the problem was, but I'm pretty sure I was > properly authenticated since I could do things like updating lists. > > > Regards > Roger > > > On Aug 31, 10:09 pm, Roger Ertesvåg <[email protected]> wrote: >> Hi Matt, >> thanks for your thorough response. >> >> So I assume this rate limit would be IP based then? I did some tests >> and got different rate limits on the server and on my development >> machine, which seems to support your theory that I'm not authenticated >> properly. >> >> After some more testing it seems that the problem is in the library, >> after switching to a previous version I get a rate limit of 350. I >> will do some more testing tomorrow to confirm this. >> >> Again, thanks for your help. >> >> Regards >> Roger >> >> On Aug 31, 8:34 pm, Matt Harris <[email protected]> wrote: >> >> > Hey Roger, >> >> > Thanks for sharing your code. A few things about the rate limits you are >> > seeing: >> >> > The 150 rate limit is for non-authenticated requests to the Twitter >> > API. These requests happen when no user identifying details are sent. >> > The 350 rate limit is for OAuth authenticated requests to the Twitter >> > API. These requests happen when you send a user token and secret. >> >> > As you are not authenticating with Basic Auth in any of your requests >> > you would only see the unauthenticated rate limit (150) or your OAuth >> > rate limit (350). The reason you could be seeing 150 is that the token >> > and secret you have are no longer valid - although in that situation I >> > would expect us to return an error saying "Could not authenticate with >> > OAuth. I'll be looking into other reasons why that might be happening >> > later today. >> >> > Hope that explains what you are seeing, >> > Matt >> >> > On Tue, Aug 31, 2010 at 12:39 AM, Roger Ertesvåg <[email protected]> >> > wrote: >> > > Hi, >> > > I'm using the ruby twitter gem: >> >> > >http://github.com/jnunemaker/twitter >> >> > > So to set it up I do: >> >> > > oauth = Twitter::OAuth.new(CONFIG['twitter_key'], >> > > CONFIG['twitter_secret']) >> > > oauth.authorize_from_access(CONFIG['twitter_atoken'], >> > > CONFIG['twitter_asecret']) >> > > base = Twitter::Base.new(oauth) >> >> > > Then when I do: >> >> > > base.rate_limit_status >> >> > > I get: >> >> > > <#Hashie::Mash hourly_limit=150 remaining_hits=150 reset_time="Tue Aug >> > > 31 08:26:37 +0000 2010" reset_time_in_seconds=1283243197> >> >> > > If I use the exact same code for other accounts I have I get: >> >> > > <#Hashie::Mash hourly_limit=350 remaining_hits=350 reset_time="Tue Aug >> > > 31 08:22:40 +0000 2010" reset_time_in_seconds=1283242960> >> >> > > Also, if I was not authorized by OAuth shouldn't the limit be even >> > > lower? >> >> > > Regards >> > > Roger >> >> > > On Aug 31, 1:03 am, Matt Harris <[email protected]> wrote: >> > >> Hi Roger, >> >> > >> It sounds like the OAuth part of your request isn't being seen by our >> > >> servers. A rate limit of 150 will be reported whenever you make a >> > >> request without authorisation. Can you share the code you are using to >> > >> make the requests so we can see what might be going wrong? >> >> > >> Thanks, >> > >> Matt >> >> > >> On Mon, Aug 30, 2010 at 11:30 AM, Roger Ertesvåg <[email protected]> >> > >> wrote: >> > >> > The OAuth rate limit for one of my accounts is stuck at 150. From what >> > >> > I'm reading, and seeing from other accounts I have, it is my >> > >> > understanding that it should be 350. What can I do to fix this? >> >> > >> > Regards >> > >> > Roger Ertesvag >> >> > >> > -- >> > >> > Twitter developer documentation and >> > >> > resources:http://dev.twitter.com/doc >> > >> > API updates via Twitter:http://twitter.com/twitterapi >> > >> > Issues/Enhancements >> > >> > Tracker:http://code.google.com/p/twitter-api/issues/list >> > >> > Change your membership to this >> > >> > group:http://groups.google.com/group/twitter-development-talk?hl=en >> >> > >> -- >> >> > >> Matt Harris >> > >> Developer Advocate, Twitterhttp://twitter.com/themattharris >> >> > > -- >> > > Twitter developer documentation and resources:http://dev.twitter.com/doc >> > > API updates via Twitter:http://twitter.com/twitterapi >> > > Issues/Enhancements >> > > Tracker:http://code.google.com/p/twitter-api/issues/list >> > > Change your membership to this >> > > group:http://groups.google.com/group/twitter-development-talk?hl=en >> >> > -- >> >> > Matt Harris >> > Developer Advocate, Twitterhttp://twitter.com/themattharris >> >> > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en > -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
