Why can¹t your application itself track this information? If it¹s a web app, it should be trivial... If it¹s any other kind of app if it can connect to Twitter, it should also be able to connect to your web service and periodically check in... That way you¹ll have accurate info up to the last tweet, as opposed to extrapolating a random sample and piping millions of tweets to find those that were send with your app.
On 3/25/10 1:27 PM, "John Kalucki" <j...@twitter.com> wrote: > Streaming API, /1/statuses/sample.json. > > http://groups.google.com/group/twitter-development-talk/browse_frm/thread/735e > b1d3ac718cbe/fbf0b331255868b6?lnk=gst&q=confidence+interval#fbf0b331255868b6 > > -John Kalucki > http://twitter.com/jkalucki > Twitter, Inc. > > > On Thu, Mar 25, 2010 at 12:37 PM, metawops <metaw...@googlemail.com> wrote: >> Hi, >> if I want to write an application that counts how many tweets are >> being made with my (officially with its own source parameter >> registered) Twitter client -- what API technique should I use? >> - the search API? >> - the streaming API? >> - the normal REST API? >> >> Streaming API currently only offers 5 or 15 % of all public tweets, >> right? :-( >> >> Thanks a lot! >> Stefan. >> >> To unsubscribe from this group, send email to >> twitter-development-talk+unsubscribegooglegroups.com >> <http://unsubscribegooglegroups.com> or reply to this email with the words >> "REMOVE ME" as the subject. > > > To unsubscribe from this group, send email to > twitter-development-talk+unsubscribegooglegroups.com or reply to this email > with the words "REMOVE ME" as the subject. > To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
