You should use the Streaming API for large scale integrations. We're not doing much whitelisting for the REST API at the moment, but the shadow role on the Streaming API is generally available. If all of your users are public, use the shadow role on stream.twitter.com/1/statuses to get all of their statuses, but not their timelines. This feature has been in production for over a year.
If you have OAuth tokens for the users, you can use the Site Streams beta to get protected user's statuses, but currently you will also get a lot of other information for them as well. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Tue, Sep 7, 2010 at 6:39 AM, Tom van der Woerdt <i...@tvdw.eu> wrote: > 1) Yes: the timelines are easier to use and more flexible, while the > streaming API gives you realtime statuses and no problems with rate limits. > 2) Streams. I'm not part of the Twitter team, but I really think that > they would recommend Streams. Of course, it depends a bit on the situation. > 3) I think so, yes. > > Tom > > > On 9/7/10 3:31 PM, Rajat wrote: > > Hi All, > > > > I am a bit torn on which API to use for my application. Have looked in > > twitter dev pages and did search internet but couldn't find > > comprehensive information. > > > > I need to get tweets from certain users in my application. I don't > > know how many users at this moment but I would like to build a > > scalable solution. I don't care if the tweets are not received real > > time as long as the delay is not in hours or days. > > > > My understanding is that I could either use streaming API (statuses/ > > filter) or timelines (friends_timeline). > > > > 1) Is there a reason for someone to use one over other (other than > > real time updates using streaming api)? > > 2) Which method twitter team recommends developer to use for future > > applications? > > 3) Are streaming APIs available for production? > > > > Sorry if some or all of these questions are already answered > > somewhere. I couldn't locate the information hence posting here. > > > > Any inputs in this regard will be greatly appreciated. > > > > Thanks in advance, > > Rajat > > > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en