[twitter-dev] Re: Saerch API and Twitter Live Search Results disparity
What is considered popular results (high-velocity)? high-velocity? Any official documentation that define the differences between Search Stream API? in terms of result quality, data size, data rate, etc If I would have to capture every single Tweet like someone asking for medical emergency, should I use Stream API? You can't just ignore a single emergency tweet b/c it is not popular. On Jun 4, 9:27 pm, Jonathan Reichhold jonathan.reichh...@gmail.com wrote: The stream API will have more results and will give all results versus the search API which will sample popular results (high-velocity), but for this case all results are available for both systems. Jonathan On Fri, Jun 4, 2010 at 9:12 PM, Bess bess...@gmail.com wrote: This is related to cache. Search API results are from cache to improve performance? Search API is not getting the same results as Stream API? On Jun 4, 3:12 pm, Jonathan Reichhold jonathan.reichh...@gmail.com wrote: This is actually an artifact of how retweets are displayed between search.twitter.com and twitter.com The tweets are there, but the display is different. Jonathan On Fri, Jun 4, 2010 at 10:10 AM, Brian Maso br...@blumenfeld-maso.com wrote: Last night I collected tweets through the search API for the hashtag #glossgreen, and got a sizeable number of tweets. This morning I did the equivalent thing through the search box on my Twitter homepage (the URL that appears in my browser is http:// twitter.com/#search?q=%23glossgreen), and got different results. More specifically, I found that there were a few users who's tweets appeared when doing the search through the search box in the browser who do not appear at all through the search API results. For example, the user @gloss had many tweets using the #glossgreen hashtag in the time period around 6-8 pm PDT 6/2 -- none of these appear in the twitter search results, but many appear in results through the twitter search box on my personal twitter homepage. I just re-performed both searches this morning to make sure this isn't a temporary issue, but got the same disparity, What expectation should I have about search API accuracy? Shold I expect the search API results to eventually repair, or is are the @gloss tweets permanently missing from the search API's database? I don't want to have to use multiple different APIs/screen-scrapes/ streams just to make sure I get accurate search results, but if that's what I have to do then please let me know. Brian Maso
Re: [twitter-dev] Re: Saerch API and Twitter Live Search Results disparity
If you need every Tweet, you need the Streaming API. Watch for limit messages -- if you are getting them, refine your predicates, or apply for higher access. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Sat, Jun 5, 2010 at 4:34 PM, Bess bess...@gmail.com wrote: What is considered popular results (high-velocity)? high-velocity? Any official documentation that define the differences between Search Stream API? in terms of result quality, data size, data rate, etc If I would have to capture every single Tweet like someone asking for medical emergency, should I use Stream API? You can't just ignore a single emergency tweet b/c it is not popular. On Jun 4, 9:27 pm, Jonathan Reichhold jonathan.reichh...@gmail.com wrote: The stream API will have more results and will give all results versus the search API which will sample popular results (high-velocity), but for this case all results are available for both systems. Jonathan On Fri, Jun 4, 2010 at 9:12 PM, Bess bess...@gmail.com wrote: This is related to cache. Search API results are from cache to improve performance? Search API is not getting the same results as Stream API? On Jun 4, 3:12 pm, Jonathan Reichhold jonathan.reichh...@gmail.com wrote: This is actually an artifact of how retweets are displayed between search.twitter.com and twitter.com The tweets are there, but the display is different. Jonathan On Fri, Jun 4, 2010 at 10:10 AM, Brian Maso br...@blumenfeld-maso.com wrote: Last night I collected tweets through the search API for the hashtag #glossgreen, and got a sizeable number of tweets. This morning I did the equivalent thing through the search box on my Twitter homepage (the URL that appears in my browser is http:// twitter.com/#search?q=%23glossgreen), and got different results. More specifically, I found that there were a few users who's tweets appeared when doing the search through the search box in the browser who do not appear at all through the search API results. For example, the user @gloss had many tweets using the #glossgreen hashtag in the time period around 6-8 pm PDT 6/2 -- none of these appear in the twitter search results, but many appear in results through the twitter search box on my personal twitter homepage. I just re-performed both searches this morning to make sure this isn't a temporary issue, but got the same disparity, What expectation should I have about search API accuracy? Shold I expect the search API results to eventually repair, or is are the @gloss tweets permanently missing from the search API's database? I don't want to have to use multiple different APIs/screen-scrapes/ streams just to make sure I get accurate search results, but if that's what I have to do then please let me know. Brian Maso
[twitter-dev] Re: Saerch API and Twitter Live Search Results disparity
This is related to cache. Search API results are from cache to improve performance? Search API is not getting the same results as Stream API? On Jun 4, 3:12 pm, Jonathan Reichhold jonathan.reichh...@gmail.com wrote: This is actually an artifact of how retweets are displayed between search.twitter.com and twitter.com The tweets are there, but the display is different. Jonathan On Fri, Jun 4, 2010 at 10:10 AM, Brian Maso br...@blumenfeld-maso.comwrote: Last night I collected tweets through the search API for the hashtag #glossgreen, and got a sizeable number of tweets. This morning I did the equivalent thing through the search box on my Twitter homepage (the URL that appears in my browser is http:// twitter.com/#search?q=%23glossgreen), and got different results. More specifically, I found that there were a few users who's tweets appeared when doing the search through the search box in the browser who do not appear at all through the search API results. For example, the user @gloss had many tweets using the #glossgreen hashtag in the time period around 6-8 pm PDT 6/2 -- none of these appear in the twitter search results, but many appear in results through the twitter search box on my personal twitter homepage. I just re-performed both searches this morning to make sure this isn't a temporary issue, but got the same disparity, What expectation should I have about search API accuracy? Shold I expect the search API results to eventually repair, or is are the @gloss tweets permanently missing from the search API's database? I don't want to have to use multiple different APIs/screen-scrapes/ streams just to make sure I get accurate search results, but if that's what I have to do then please let me know. Brian Maso
Re: [twitter-dev] Re: Saerch API and Twitter Live Search Results disparity
This has nothing to do with the cache. Speaking as a engineer in the search group I can state that this has nothing to do with the cache. Jonathan @jreichhold On Fri, Jun 4, 2010 at 9:12 PM, Bess bess...@gmail.com wrote: This is related to cache. Search API results are from cache to improve performance? Search API is not getting the same results as Stream API? On Jun 4, 3:12 pm, Jonathan Reichhold jonathan.reichh...@gmail.com wrote: This is actually an artifact of how retweets are displayed between search.twitter.com and twitter.com The tweets are there, but the display is different. Jonathan On Fri, Jun 4, 2010 at 10:10 AM, Brian Maso br...@blumenfeld-maso.com wrote: Last night I collected tweets through the search API for the hashtag #glossgreen, and got a sizeable number of tweets. This morning I did the equivalent thing through the search box on my Twitter homepage (the URL that appears in my browser is http:// twitter.com/#search?q=%23glossgreen), and got different results. More specifically, I found that there were a few users who's tweets appeared when doing the search through the search box in the browser who do not appear at all through the search API results. For example, the user @gloss had many tweets using the #glossgreen hashtag in the time period around 6-8 pm PDT 6/2 -- none of these appear in the twitter search results, but many appear in results through the twitter search box on my personal twitter homepage. I just re-performed both searches this morning to make sure this isn't a temporary issue, but got the same disparity, What expectation should I have about search API accuracy? Shold I expect the search API results to eventually repair, or is are the @gloss tweets permanently missing from the search API's database? I don't want to have to use multiple different APIs/screen-scrapes/ streams just to make sure I get accurate search results, but if that's what I have to do then please let me know. Brian Maso
Re: [twitter-dev] Re: Saerch API and Twitter Live Search Results disparity
The stream API will have more results and will give all results versus the search API which will sample popular results (high-velocity), but for this case all results are available for both systems. Jonathan On Fri, Jun 4, 2010 at 9:12 PM, Bess bess...@gmail.com wrote: This is related to cache. Search API results are from cache to improve performance? Search API is not getting the same results as Stream API? On Jun 4, 3:12 pm, Jonathan Reichhold jonathan.reichh...@gmail.com wrote: This is actually an artifact of how retweets are displayed between search.twitter.com and twitter.com The tweets are there, but the display is different. Jonathan On Fri, Jun 4, 2010 at 10:10 AM, Brian Maso br...@blumenfeld-maso.com wrote: Last night I collected tweets through the search API for the hashtag #glossgreen, and got a sizeable number of tweets. This morning I did the equivalent thing through the search box on my Twitter homepage (the URL that appears in my browser is http:// twitter.com/#search?q=%23glossgreen), and got different results. More specifically, I found that there were a few users who's tweets appeared when doing the search through the search box in the browser who do not appear at all through the search API results. For example, the user @gloss had many tweets using the #glossgreen hashtag in the time period around 6-8 pm PDT 6/2 -- none of these appear in the twitter search results, but many appear in results through the twitter search box on my personal twitter homepage. I just re-performed both searches this morning to make sure this isn't a temporary issue, but got the same disparity, What expectation should I have about search API accuracy? Shold I expect the search API results to eventually repair, or is are the @gloss tweets permanently missing from the search API's database? I don't want to have to use multiple different APIs/screen-scrapes/ streams just to make sure I get accurate search results, but if that's what I have to do then please let me know. Brian Maso
