Josh: The obvious thing is to register you app and then authenticate with OAuth. You will then have your very own rate limit to consume based on the application name.
On Oct 20, 4:57 pm, Josh <godatp...@gmail.com> wrote: > Yeah...I forgot about the whole shared host thing. That really > sucks. My application uses all unauthenticated calls, so there's > nothing I can do, right? That's what I got from the rate limiting > page. > > On Oct 20, 6:35 pm, Slate Smith <sl...@slatesmith.com> wrote: > > > > > > > > > Yeah unfortunately rate limits are checked via IP AND App keys, so if > > it's a shared server ... I don't think that you can see unless you > > have access to the server logs [doubtful at best] > > > - S. -- 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
