> The Terms say: "We do not rate limit the search API under ordinary > circumstances, however we have put measures in place to limit the > abuse of our API."
...yes, which is exactly why I am asking the question in the first place. My code already handles the error case so no browser warnings are popped. I addressed the question to Matt originally since I thought he was the Search API guru, or am I mistaken? -Chad On Mon, Dec 8, 2008 at 10:23 AM, fastest963 <[EMAIL PROTECTED]> wrote: > > Ah, gotcha! You can, it will just display a browser warning. Which is > not what you want :P > > The Terms say: "We do not rate limit the search API under ordinary > circumstances, however we have put measures in place to limit the > abuse of our API." > Try emailing, Alex Payne, or someone at Twitter about a whitelist. > > On Dec 7, 3:36 pm, "Chad Etzel" <[EMAIL PROTECTED]> wrote: > > No, you can't do an ajax authenticated GET or POST to a 3rd-party site. > I > > am dynamically loading the json in the clients' browser. I would rather > > know the rate limits so I can abide by them. > > > > -Chad > > > > On Sun, Dec 7, 2008 at 10:42 AM, fastest963 <[EMAIL PROTECTED]> > wrote: > > > > > Since your doing this via AJAX and such, this may not be a good idea, > > > but you could try passing a login to Twitter and having that login > > > whitelisted? >
