If I remember correctly, the HTTP response code for rate limiting is something other that 200 (which doesn't really do much good if you're using a JSONP type request from a browser), so jsonifying or xmlifying that rate limit string would be useful. I suggest opening an issue for it.
As for credentials, search requests are totally unauthenticated, so you needn't send any credentials along with the search request. -Chad On Tue, Mar 3, 2009 at 1:46 PM, John Adams <[email protected]> wrote: > > Rate limiting is based on the IP address of the client. > > -j > > On Mar 3, 2009, at 10:42 AM, Dimebrain wrote: > >> >> I have experienced sending search requests out which return a plain >> string, rather than JSON representing a twitter error. It's this: >> >> "You have been rate limited. Enhance your calm." >> >> a) What is the rate limiting based on, IP or client? What is the >> limit? I develop a Twitter library (tweetsharp) and by default I send >> the tweet# credentials along with the call. If this means that anyone >> using my library will be rate limited because of that header >> information, I need to know so I can force my users to provide their >> own credentials so that the library isn't unusable in this area, and >> >> b) Can we get his as XML, JSON and not a plain string? >> > > --- > John Adams > Twitter Operations > [email protected] > http://twitter.com/netik > > > > >
