This app cannot use User Streams and must only use Site Streams. User Streams is for desktop applications now, and soon will be available for all single-user-per-host applications.
Site Streams are for all large scale integrations -- many streams to a single host, as Site Streams bundles multiple User Streams onto a single connection. To use User Streams would consume an awful lot of resources on both ends. Site Steams does and will support Home Timelines -- but we're not ready to beta this feature just yet due to a performance issue that we're working through. -John Kalucki http://twitter.com/jkalucki Twitter Inc. On Mon, Sep 6, 2010 at 11:36 PM, Rainux <rai...@gmail.com> wrote: > Hello, I'm writing a Twitter client that acts as a XMPP bot. Users can > add the bot as buddy then bind their Twitter account, after that the > bot will use Streaming API to push home/mentions/dm and other user > interested stuffs to them. I found User Streams is suitable for this > since Site Streams not support home timeline. > > Does my app conflict with Twitter's rules about User Streams? > > -- > 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