We haven't made any decisions about Basic Auth and the Streaming API. Yes, the policy is vague about connection cardinality. We're still in beta...
-John On Fri, Sep 17, 2010 at 3:31 PM, M. Edward (Ed) Borasky < zn...@borasky-research.net> wrote: > -- > M. Edward (Ed) Borasky > http://borasky-research.net http://twitter.com/znmeb > > "A mathematician is a device for turning coffee into theorems." - Paul > Erdos > > > > Quoting John Kalucki <j...@twitter.com>: > > Posted here: http://dev.twitter.com/pages/streaming_api >> >> There are three main Streaming products: The Streaming API, User Streams >> and >> Site Streams. These products operate in the same way, but each serves a >> somewhat different purpose. >> >> - *Streaming API:* Public statuses from all users, filtered in various >> ways: By userid, by keyword, by random sampling, by geographic location, >> etc. >> > > Requires authentication, currently accepts either basic or oAuth, right? > oAuth mandatory at some future date? > > > Handful is five, right? ;-) > > -- 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
