The streaming API supports basic auth *now*. At some point in the future it will not. If you're developing something new with basic auth you're setting yourself up for more work in the not too distant future.
As far as the present message, only userstreams and sitestreams require oauth currently, so it's not likely an oauth issue. ---Mark http://twitter.com/mccv On Tue, Nov 2, 2010 at 2:27 PM, EastSideDev <eastside...@gmail.com> wrote: > I've been using the streaming library in one of my apps. My > understanding is that the streaming API still supports Basic > Authentication, so I don't need to make any changes. My app did stop > working with messages indicating that I am not being properly > authenticated. Do I need to switch to oAuth here as well (not 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 > -- 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