Dewald, I'm not on the search team, but there are a lot of discussions over there this morning about search api rate limits and related issues. Search rate limiting issues (vs. www.twitter.com or api.twitter.com) probably boil down to one of three categories:
1) Search service interruptions - We're working on these, obviously. You may see odd behavior when search capacity is reduced due to some operational issue, and the system is running far too hot. 2) General API limit reductions - We're slightly less generous than we have been in the past due to persistent abuse of the search api and due to overall capacity issues. We can't always provide for all valid use cases, although that is certainly a high priority. 3) Bugs. There could be defects that prevent valid use of the API. Detailed data of limiting mishaps would be helpful here. Timestamps, queries and statistics around reasonable use that was denied may allow us to identify a previously unknown defect. The search team is quite interested in working on #3. -John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Sep 1, 5:41 pm, Dewald Pretorius <dpr...@gmail.com> wrote: > Twitter team, can you please do something about the performance and > rate limiting of the Search API. > > It is becoming completely unworkable. I have jumped through all the > hoops, with unique User Agents, sleeping my scripts in-between API > calls, and yet the rate limiting is just becoming more severe, and the > performance is just becoming slower and slower. > > Please help. A lot of us are using Search to provide services, and I > am sure it is not only my service that is hurting very much under the > present circumstances. > > Dewald
