> The key to max search results isn't in paging or rpp, but
> in max_id.
Hi David,
I do not understand how max_id can help me.
If I want to get the 10,000 most recent tweets that match
the phrase "michael jackson" changing the max_id value
doesn't seem like it's going to help at all.
In fa
The rpp defaults to 15 or something if you don't specify it. Sounds
like you need to mess around and play with things a bit more.
The key to max search results isn't in paging or rpp, but in max_id.
Be careful what you ask for. Retrieval of everything available can
take a long time (hours)
dave
I don't have a domain to point back to. I'm doing data-mining and
analysis on a server that isn't public.
I have set the User-Agent to something unique (I thought you were
saying to change it for every request?).
Yet I'm still getting rate limited and told to back off a lot. Ryan S
said it might s
The referrer is not as important as the user-agent. You can also put
your URL in the user-agent instead.
-Chad
On Tue, Aug 11, 2009 at 4:09 PM, Larry Wright wrote:
> In addition to setting a unique user-agent, I believe it was requested that
> we set a referrer header that pointed back to a domai
In addition to setting a unique user-agent, I believe it was requested that
we set a referrer header that pointed back to a domain.
On Tue, Aug 11, 2009 at 9:30 AM, David Fisher wrote:
>
> While i haven't done scientific testing of this, I was able to run up
> to 3-4 instances of my search scrip
Hi Dave,
I'm not sure which twitter wrapper you are using. But if you're using Dan
Croak's from here:
http://github.com/dancroak/twitter-search
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".
Yu-Shan
David,
I don't know Ruby, so I don't know if this is possible.
But, if possible you need to edit your copy of the Twitter API wrapper
and set the user agent to something that is unique to your service.
If you use the same user agent as everyone else who are using that
wrapper, then you are goin
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.
dave
On Aug 11, 10:36 am, Andrew Badera wrote:
> On Tue, Aug 11, 2009 at 10:30 AM, David Fisher wrote:
>
> > Wh
On Tue, Aug 11, 2009 at 10:30 AM, David Fisher 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 delay
