I'm not sure which twitter wrapper you are using. But if you're using Dan
Croak's from here:
You might need to update your gem, and make sure you specify the name of
your app as the "agent" instead of using the default "twitter-search".
On Tue, Aug 11, 2009 at 10:45 AM, David Fisher <tib...@gmail.com> wrote:
> The user agent for each search request is the same. I'm using the Ruby
> Twitter API wrapper, so sending anything else with search requests
> isn't possible unless that is now deprecated.
> On Aug 11, 10:36 am, Andrew Badera <and...@badera.us> wrote:
> > On Tue, Aug 11, 2009 at 10:30 AM, David Fisher<tib...@gmail.com> wrote:
> > > While i haven't done scientific testing of this, I was able to run up
> > > to 3-4 instances of my search script prior at a time before it told me
> > > to enhance my calm. Now I'm barely able to run one without hitting the
> > > limit. I can put delays in my code to slow it down, but I'm wondering
> > > if this is just a symptom of the aftermath of the DDoS attack or
> > > something else? My server has a dedicated IP and no one else runs code
> > > from it, so it isn't other people on my IP hitting the Search API.
> > > Maybe I need to talk about Search API whitelisting...
> > > dave
> > >http://webecologyproject.org
> > Are you sending a unique client ID header with each request, per
> > previous Search API throttling conversations? (Not sure that it
> > matters, that seemed pretty fuzzy when discussed ...)
> > ∞ Andy Badera
> > ∞ This email is: [ ] bloggable [x] ask first [ ] private
> > ∞ Google me:
“When nothing seems to help, I go look at a stonecutter hammering away at
his rock perhaps a hundred times without as much as a crack showing in it.
Yet at the hundred and first blow it will split in two, and I know it was
not that blow that did it, but all that had gone before.” — Jacob Riis