[twitter-dev] API Search Method: Question on "since" operator

2010-10-05 Thread Satish
Hi,

In the search API, the documentation says the "since" operator returns
a HTTP 404 error if it is too old.

How to determine if a date is too old for searching? In general, up to
what date in the past will the API returns data?

Thanks
Satish

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] API Search

2009-09-09 Thread Gustavo Melo

Why the parameter "near" is not avaible for api search on twitter?

What i can't understand is...

I can search on search.twitter.com this query:@twitter OR @twitterapi
near:Brasil
http://search.twitter.com/search...@twitter+or+@twitterapi+near:Brasil

If i click on Feed for this query i can get this result for the query
above:
http://search.twitter.com/search.atom?geocode=-14.235004,-51.92528,2500.0km&lang=en&q...@twitter+or+@twitterapi+near:Brasil

if i change atom for json, it's ok.

but it's not possible to do this: (without geocode parameter)
http://search.twitter.com/search.atom?lang=en&q...@twitter+or+@twitterapi+near:Brasil

So, why i can't just use near with api??
How i get the geocode with api??
How i get this feed with api??

Best Regards.


[twitter-dev] API search, json results, 404 pages, and docs

2009-06-29 Thread talklists

http://search.twitter.com/search.json?page=4&max_id=2384515303&rpp=80&q=from%3Acometbus

I have hit page 4 on that request.
Here is the JSON I am getting back:
{
"results": [],
"since_id": 0,
"max_id": 2384515303,
"previous_page": "?page=3&max_id=2384515303&rpp=80&q=from
%3Acometbus",
"refresh_url": "?since_id=2384515303&q=from%3Acometbus",
"results_per_page": 80,
"total": 240,
"completed_in": 0.273265,
"page": 4,
"query": "from%3Acometbus"
}

This account has 1600 updates, so rpp(80)*4 = 320, which is much less
than 1600.  The above is also a 404 page.  I have read the docs which
tell me the below conflicting information.

http://apiwiki.twitter.com/Things-Every-Developer-Should-Know#6Therearepaginationlimits
 Search API Limit Clients may request up to 1,500 statuses
 via the page and rpp parameters for the search method. The
 response to a request exceeding this limit will be a
 status code of 200 and an empty result in the format
 requested. This artificial limit is in place to ensure the
 performance of the search system. We also restrict the
 size of the search index by placing a date limit on the
 updates we allow you to search. This limit is currently
 around 1.5 weeks but is dynamic and subject to shrink as
 the number of tweets per day continues to grow.

I do not get a 200 response, I get a 404 response.  I can not go back
as far as I would like to.  Interestingly, the twitter website, as
well as tweetie client can go back much farther with no issue.

Thanks.