Yaemog: You are right, he does say he is posting to his Twitter Page and that he is using oAuth. My bad...
So there is something else going on. - Check that authentication was successful. The rate limit should be higher if he has successfully authenticated. - Check the return message from Twitter. When I see a 403 Twitter also sends a response that tells me why the 403 was returned. - Make sure there is no other program using the same Twitter Application name; the other application will draw down the rate limit. On Nov 2, 10:00 am, yaemog Dodigo <[email protected]> wrote: > > You mention 150/hour so I am guessing that you are not authenticating > > with Twitter. This means that if there are any other applications > > sharing the same IP address (shared hosting) then they are also using > > the same rate limit as your app. If you authenticate you will get the > > 250/hour ratelimit and it will be all yours to consume. > > > Dave > > Hi Dave, > > When I read Peter's post, I thought of the same thing. However, since he is > successfully posting, wouldn't that require to be authenticated? > > --d -- 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
