We're not forcing people over to Site Streams. If, on the other hand, if you start to consume Site Streams, we want you to stop regular polling on the REST API.
If your service is modest, any excess delivery will be modest. Excessive options add complexity and slow development for what may be little practical efficiency gain. Bandwidth and CPU are nearly free at 1mbit/sec. It's all a balance. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Mon, Aug 30, 2010 at 12:15 PM, Dewald Pretorius <dpr...@gmail.com> wrote: > This is super news. > > However, if you're going to force web services to use Site Streams > when it is in production ("sites must only use the REST API for data > that is not available through User Streams"), then please add the > ability to subscribe only to certain elements. For example, we need > the ability to subscribe to only Follows, or to only Tweets and > Retweets, etc. > > You make note that each stream may consume significant bandwidth (> > 1MB). > > If a web service does not make use of the user's Follows, or of the > user's Tweets, then it makes no sense to consume that bandwidth with > the dead-weight of the elements that are not used by the service. > > I understand that Site Streams is in beta now. I'm putting in this > request for when it is in production and we are forced to use it. > > -- > 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