[twitter-dev] Re: Track vs. Search
If you want a larger proportion of the statuses, you can apply for a higher level of track access. -John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Aug 22, 8:17 am, Mark Nutter marknut...@gmail.com wrote: @Will Yeah, that's what we're currently using, and it works well enough, but I would really love an unthrottledtrackbecause it includes the user profile information inline. That would be sooo nice. On Aug 20, 11:54 am, Wil Kern w...@tweetmart.com wrote: Have you thought about just using the filter:links in yoursearchquery? Will On Thu, Aug 20, 2009 at 10:21 AM, Mark Nutter marknut...@gmail.com wrote: I'm writing an application that needs a realtime stream of the links being posted on Twitter. I've been using thesearchapi with asearch for the term 'http' but I stumbled across thetrackfirehose method which appears to offer the same functionality but with the added bonus of including the user profile information inline. Doestrackprovide the same real-time stream that thesearchapi does? Would I be missing links at all by usingtrack? If not, I'll switch over to that immediately. This will greatly reduce the number of API calls I need to make to update user information. Thanks! -- Will Kernwww.tweetmart.com (c) 703-431-9393
[twitter-dev] Re: Track vs. Search
No, and Yes. Track does not allow for getting that high of a number of results, you will be throttled, thus you will miss links. -Joel On Thu, Aug 20, 2009 at 7:21 AM, Mark Nutter marknut...@gmail.com wrote: I'm writing an application that needs a realtime stream of the links being posted on Twitter. I've been using the search api with a search for the term 'http' but I stumbled across the track firehose method which appears to offer the same functionality but with the added bonus of including the user profile information inline. Does track provide the same real-time stream that the search api does? Would I be missing links at all by using track? If not, I'll switch over to that immediately. This will greatly reduce the number of API calls I need to make to update user information. Thanks!
[twitter-dev] Re: Track vs. Search
Have you thought about just using the filter:links in your search query? Will On Thu, Aug 20, 2009 at 10:21 AM, Mark Nutter marknut...@gmail.com wrote: I'm writing an application that needs a realtime stream of the links being posted on Twitter. I've been using the search api with a search for the term 'http' but I stumbled across the track firehose method which appears to offer the same functionality but with the added bonus of including the user profile information inline. Does track provide the same real-time stream that the search api does? Would I be missing links at all by using track? If not, I'll switch over to that immediately. This will greatly reduce the number of API calls I need to make to update user information. Thanks! -- Will Kern www.tweetmart.com (c) 703-431-9393
