[twitter-dev] Re: Search queries not working

Hi there, Can you provide an example URL where since_id isn't working so I can try and reproduce the issue? As for language, the language identifier is not a 100% and sometimes makes mistakes. Hopefully not too many mistakes but it definitely does. Thanks; — Matt Sanford / @mzsanfo

[twitter-dev] Re: Search queries not working

HI Matt, when Since_id and Max_id are given together, max_id is not working. This query is ignoring max_id. But with only since _id its working fine. Is there any problem when max_id and since_id are used together. Also please tell me what does max_id exactly mean and also what does it return whe

[twitter-dev] Re: Search queries not working

Hi Basha, The max_id is only intended to be used for pagination via the next_url and prev_url fields and is known not to work with since_id. It is not documented as a valid parameter because it's known to only work in the case it was designed for. We added the max_id to prevent the pr

[twitter-dev] Re: Search queries not working

Hi Matt, I have tried to use language parameter of twitter search and find the result is very unreliable. For example: http://search.twitter.com/search?lang=all&q=tweetjobsearch returns 10 results (all in english), but http://search.twitter.com/search?lang=en&q=tweetjobsearch only returns 3. I g

[twitter-dev] Re: Search queries not working

Hi matt, Thank You What is Pagination? Does it mean that I cannot use max_id for searching tweets. What does next_url and prev_url fields mean. I did not find next_url and prev_url in documentation. how can these two urls be used with max_id. Please explain with example if possible. Regards, M

[twitter-dev] Re: Search queries not working

Basha, Pagination is defined well here [1]. The next_url and prev_url fields give your client HTTP URIs to move forward and backward through the result set. You can use them to page through search results. I have some work to do on the search docs and I'll add field definitions then as well. 1.

[twitter-dev] Re: Search queries not working

HI, Can you give me an example how i can use prev_url and next_url with max_id. No I am following below process to search 1. Set rpp=100 and retrieve 15 pages search results by incrementing the param 'page' 2. Get the id of the last status on page 15 and set that as the max_id for the next quer

[twitter-dev] Re: Search queries not working

The use of prev_url and next_url will take care of step 1 from your flow described above. Specifically, next_url will give your application the URI to contact to get the next page of results. Combining max_id and next_url usage will not solve the duplicate problem. To overcome that issue, you wil

[twitter-dev] Re: Search queries not working

I'm not sure of these "next_url" and "prev_url" fields (never seen them anywhere), but at least in the json data there is a "next_page" field which uses "?page=_&max_id=__" already prefilled for you. This should definitely avoid the duplicate tweet issue. I've never had to do any client-side

[twitter-dev] Re: Search queries not working

Hi Chad, how can we use "next_page" in the url we request. where can we get the url we need to pass. Regards, Mahaboob Basha Shaik www.netelixir.com Making Search Work On Fri, Apr 3, 2009 at 7:14 PM, Chad Etzel wrote: > > I'm not sure of these "next_url" and "prev_url" fields (never seen > t

[twitter-dev] Re: Search queries not working

Are you using the .atom or .json API feed? I am only familiar with the .json feed. -Chad On Sat, Apr 4, 2009 at 2:01 AM, Basha Shaik wrote: > Hi Chad, > > how can we use "next_page" in the url we request. where can we get the url > we need to pass. > > Regards, > > Mahaboob Basha Shaik > www.ne

[twitter-dev] Re: Search queries not working

I am using json Regards, Mahaboob Basha Shaik www.netelixir.com Making Search Work On Sat, Apr 4, 2009 at 6:07 AM, Chad Etzel wrote: > > Are you using the .atom or .json API feed? I am only familiar with > the .json feed. > -Chad > > On Sat, Apr 4, 2009 at 2:01 AM, Basha Shaik > wrote: > >

[twitter-dev] Re: Search queries not working

Assuming you get the json data somehow and store it in a variable called "jdata", you can construct the next page url thus: var next_page_url = "http://search.twitter.com/"; + jdata.next_page; -Chad On Sat, Apr 4, 2009 at 2:11 AM, Basha Shaik wrote: > I am using json > > Regards, > > Mahaboob

[twitter-dev] Re: Search queries not working

Hi Doug, you said we can use next_url and prev URL. I tried to get next_url. the response is saying that there is no field called next_url. Should i pass next _url in the request with max_id? if so how can i know what next_url is? Can u give an clear example how to use prev_url and next_url Rega

[twitter-dev] Re: Search queries not working

Sorry, typo previously: var next_page_url = "http://search.twitter.com/search.json"; + jdata.next_page; On Sat, Apr 4, 2009 at 2:18 AM, Chad Etzel wrote: > Assuming you get the json data somehow and store it in a variable > called "jdata", you can construct the next page url thus: > > var next_

[twitter-dev] Re: Search queries not working

Hi Chad, how can we store all json data in a variable "jdata". Can you tell me how to do that? I am using java for jason processing Which technology are you using? Regards, Mahaboob Basha Shaik www.netelixir.com Making Search Work On Sat, Apr 4, 2009 at 6:23 AM, Chad Etzel wrote: > > Sorry, t

[twitter-dev] Re: Search queries not working

My example was in javascript. How are you retrieving the json data? What language are you using? -chad On Sat, Apr 4, 2009 at 2:35 AM, Basha Shaik wrote: > Hi Chad, > how can we store all json data in a variable "jdata". > Can you tell me how to do that? > I am using java for jason processing >

[twitter-dev] Re: Search queries not working

Hi i am using java. We parse the json response. and store the value as key - value pairs in a Map. In the reponse no wahere i found next_url or next_page. Can you tell me how we can store all json data in a variable. Regards, Mahaboob Basha Shaik www.netelixir.com Making Search Work On Sat, Ap

[twitter-dev] Re: Search queries not working

I have not used java in a long time, but there should be a "next_page" key in the map you create from the json response. Here is an example json response with rpp=1 for "hello": {"results":[{"text":"hello","to_user_id":null,"from_user":"fsas1975","id":1450457219,"from_user_id":6788389,"source":"

[twitter-dev] Re: Search queries not working

Hi chad, Thank you. I was trying for a query which has only 55 tweets and i have kept 100 as rpp . so i was not getting next_page. when i decreased rpp to 20 and tried i got now. thank you very much. i Will check if any Duplicates occur with these and let you know. Regards, Mahaboob Basha Shaik

[twitter-dev] Re: Search queries not working

Hi Chad, No duplicates are there with this. Thank You Regards, Mahaboob Basha Shaik www.netelixir.com Making Search Work On Sat, Apr 4, 2009 at 7:29 AM, Basha Shaik wrote: > Hi chad, > > Thank you. I was trying for a query which has only 55 tweets and i have > kept 100 as rpp . so i was not get

[twitter-dev] Re: Search queries not working

Hi, Is there any Length Limit in the query I pass in search API? Regards, Mahaboob Basha Shaik www.netelixir.com Making Search Work On Sat, Apr 4, 2009 at 10:27 AM, Basha Shaik wrote: > Hi Chad, > No duplicates are there with this. > Thank You > Regards, > > Mahaboob Basha Shaik > www.netelix

[twitter-dev] Re: Search queries not working

Yes. Queries are limited to 140 characters. Basha Shaik wrote: Hi, Is there any Length Limit in the query I pass in search API? Regards, Mahaboob Basha Shaik www.netelixir.com Making Search Work On Sat, Apr 4, 2009 at 10:27 AM, Basha Shaik mailto:basha.neteli...@