The Streaming API sample method would provide a random sampling of public users weighted by update rate, not a random sampling of all users. The default 'spritzer' should be sufficient for most uses.
-John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Oct 12, 8:01 am, Andrew Badera <and...@badera.us> wrote: > Doesn't the streaming API have a sampling method "status/sample" for > statuses from which you can derive users? And don't the docs describe > this as "random," while specifying gardenhose access is required for > statistically significant samples? > > ∞ Andy Badera > ∞ +1 518-641-1280 > ∞ This email is: [ ] bloggable [x] ask first [ ] private > ∞ Google me:http://www.google.com/search?q=andrew%20badera > > On Mon, Oct 12, 2009 at 10:58 AM, Ryan Rosario <uclamath...@gmail.com> wrote: > > > I am doing some research using the Twitter API and I would like to get > > a random sample of Twitter users. Any ideas of how this can be > > accomplished? > > > So far, I have scraped 2 weeks from the Streaming API and extracted 3 > > million user IDs from the stream. Any arguments as to whether or not > > this could constitute random? > > > Thanks, > > Ryan
