[twitter-dev] search randomly limits result set

2010-08-10 Thread mX.
Hullo all -

While I opted to keep the subject line short(er), I allow that this
may all be a case of user error and that there may be nothing either
random w/ the API.  That said...

... I've been working w/ the REST API and am trying to incorporate
some of the Search API functionality, but am having a very difficult
time w/ it.  An immediate example is the fact that the API seems to
return very few items from its search.

E.g., the following search strings (740AM PST, Tue Aug 10):
feed://search.twitter.com/search.atom?q=%23thenyknicks+OR+%23allan_houston
- returns 4 tweets dating back to Thu Aug 5, 110P (per Twitter
feeds)
feed://search.twitter.com/search.atom?q=%23thenyknicks+OR+%23allan_houston+OR+from%3Athenyknicks+OR+from%3Aallan_houston
- returns 13 tweets dating back  to Thu Aug 5, 601A (per Twitter
feeds)
feed://search.twitter.com/search.atom?q=%23thenyknicks+OR+%23allan_houston+OR+from%3Athenyknicks+OR+from%3Aallan_houston+OR+%232MNBA
- returns 15 tweets dating back to Sun Aug 8, 127P (per Twitter
feeds)

All the information I've read re: rate limits should put 15 tweets
well below that.  Further, although the API docs suggest the data for
the Search API is indexed only for the last seven days, I would still
expect to see tweets for all of the last seven days, rather than only
five (e.g., the first search should have returned more Tweets dating
back to Aug 3.

All in all the API does not appear to be working as advertised,
however, I may be missing the fine print.

Is there a limit on the # of days back which the search parameters
will reach? And what is it?
Is there a limit on the # of tweets that will be returned? And what is
it?

Thank you in advance!
mX.


Re: [twitter-dev] search randomly limits result set

2010-08-10 Thread Taylor Singletary
The search API's available corpus of tweets for search varies -- it's not
always exactly a week, as tweet velocity has an effect on how many tweets
can be made readily available for searching. Search also contains only a
portion of the total amount of tweets in the system at any one time:
http://support.twitter.com/groups/32-something-s-not-working/topics/118-search/articles/66018-my-tweets-or-hashtags-are-missing-from-search-known-issue

Thanks,
Taylor


On Tue, Aug 10, 2010 at 8:00 AM, mX. michael.g.xena...@gmail.com wrote:

 Hullo all -

 While I opted to keep the subject line short(er), I allow that this
 may all be a case of user error and that there may be nothing either
 random w/ the API.  That said...

 ... I've been working w/ the REST API and am trying to incorporate
 some of the Search API functionality, but am having a very difficult
 time w/ it.  An immediate example is the fact that the API seems to
 return very few items from its search.

 E.g., the following search strings (740AM PST, Tue Aug 10):
 feed://search.twitter.com/search.atom?q=%23thenyknicks+OR+%23allan_houston
- returns 4 tweets dating back to Thu Aug 5, 110P (per Twitter
 feeds)
 feed://
 search.twitter.com/search.atom?q=%23thenyknicks+OR+%23allan_houston+OR+from%3Athenyknicks+OR+from%3Aallan_houston
- returns 13 tweets dating back  to Thu Aug 5, 601A (per Twitter
 feeds)
 feed://
 search.twitter.com/search.atom?q=%23thenyknicks+OR+%23allan_houston+OR+from%3Athenyknicks+OR+from%3Aallan_houston+OR+%232MNBA
- returns 15 tweets dating back to Sun Aug 8, 127P (per Twitter
 feeds)

 All the information I've read re: rate limits should put 15 tweets
 well below that.  Further, although the API docs suggest the data for
 the Search API is indexed only for the last seven days, I would still
 expect to see tweets for all of the last seven days, rather than only
 five (e.g., the first search should have returned more Tweets dating
 back to Aug 3.

 All in all the API does not appear to be working as advertised,
 however, I may be missing the fine print.

 Is there a limit on the # of days back which the search parameters
 will reach? And what is it?
 Is there a limit on the # of tweets that will be returned? And what is
 it?

 Thank you in advance!
 mX.



Re: [twitter-dev] search randomly limits result set

2010-08-10 Thread michael xenakis
Thanks, Taylor.

And to clarify my understanding:

The Search API is the only entry point for compound searches, yes? I.e., if I 
want to get Tweets from multiple users in a single call?

Also, the REST API does not support searching for hash tags in any form, yes? 
So the Search API is the only means for that?

Thanks again,
mX.

p.s. The Search Quality Help Page link at the bottom of the page you linked 
below is dead.  I.e.,: 
http://support.twitter.com/groups/32-something-s-not-working/topics/118-search/articles/66018-my-tweets-or-hashtags-are-missing-from-search-known-issue


On Aug 10, 2010, at 8:31 AM, Taylor Singletary wrote:

 The search API's available corpus of tweets for search varies -- it's not 
 always exactly a week, as tweet velocity has an effect on how many tweets can 
 be made readily available for searching. Search also contains only a portion 
 of the total amount of tweets in the system at any one time: 
 http://support.twitter.com/groups/32-something-s-not-working/topics/118-search/articles/66018-my-tweets-or-hashtags-are-missing-from-search-known-issue
 
 Thanks,
 Taylor
 
 
 On Tue, Aug 10, 2010 at 8:00 AM, mX. michael.g.xena...@gmail.com wrote:
 Hullo all -
 
 While I opted to keep the subject line short(er), I allow that this
 may all be a case of user error and that there may be nothing either
 random w/ the API.  That said...
 
 ... I've been working w/ the REST API and am trying to incorporate
 some of the Search API functionality, but am having a very difficult
 time w/ it.  An immediate example is the fact that the API seems to
 return very few items from its search.
 
 E.g., the following search strings (740AM PST, Tue Aug 10):
 feed://search.twitter.com/search.atom?q=%23thenyknicks+OR+%23allan_houston
- returns 4 tweets dating back to Thu Aug 5, 110P (per Twitter
 feeds)
 feed://search.twitter.com/search.atom?q=%23thenyknicks+OR+%23allan_houston+OR+from%3Athenyknicks+OR+from%3Aallan_houston
- returns 13 tweets dating back  to Thu Aug 5, 601A (per Twitter
 feeds)
 feed://search.twitter.com/search.atom?q=%23thenyknicks+OR+%23allan_houston+OR+from%3Athenyknicks+OR+from%3Aallan_houston+OR+%232MNBA
- returns 15 tweets dating back to Sun Aug 8, 127P (per Twitter
 feeds)
 
 All the information I've read re: rate limits should put 15 tweets
 well below that.  Further, although the API docs suggest the data for
 the Search API is indexed only for the last seven days, I would still
 expect to see tweets for all of the last seven days, rather than only
 five (e.g., the first search should have returned more Tweets dating
 back to Aug 3.
 
 All in all the API does not appear to be working as advertised,
 however, I may be missing the fine print.
 
 Is there a limit on the # of days back which the search parameters
 will reach? And what is it?
 Is there a limit on the # of tweets that will be returned? And what is
 it?
 
 Thank you in advance!
 mX.
 



Re: [twitter-dev] search randomly limits result set

2010-08-10 Thread M. Edward (Ed) Borasky
I sometimes do a search back in time for all the tweets from Portland,  
Oregon. What I've found is that there seems to be a limit on the total  
number of tweets I can get that is independent of time. The last time  
I ran this, IIRC it returned about 3 tweets. So I suspect the  
answer is 3 tweets or as far back as the index exists, whichever  
is smaller.

--
M. Edward (Ed) Borasky
http://borasky-research.net http://twitter.com/znmeb

A mathematician is a device for turning coffee into theorems. - Paul Erdos