What about this?

I'm not interested in passwords at all, but it's not possible using oAuth
for the streaming API. You have suggested mixing the streaming API and REST
API for providing the best experience for users, but this way I have no
choice but using username/password authentication to be able to use the
streaming API.


On Tue, Jan 12, 2010 at 8:01 AM, Raffi Krikorian <ra...@twitter.com> wrote:

> As it stands, developers who have relatively new desktop apps are
>> penalized by having updates from their app say 'from web'. Older Basic
>> Auth desktop clients continue to enjoy a link back to the client web
>> site with a 'from app' link.
> ...
>> I understand Twitter is trying to force people to use OAuth, but that
>> won't happen in a meaningful way until OAuth is reliable, has a truly
>> usable workflow (PIN method isn't it), and can work well with other
>> services (Twitpic, yfrog, etc). We aren't there yet.
> i'm trying to gather use cases around OAuth to help it make sense for more
> people to use it -- as it stands, we are not going to allow the source
> parameter to be set in new applications unless they come from OAuth.  so,
> please help me out!
> is the reliability of OAuth an actual concern?  do you have a suggestion as
> to what you would like to see other than the PIN workflow?  additionally,
> we're actively working on a "delegation" method for integration with other
> services.
> --
> Raffi Krikorian
> Twitter Platform Team
> http://twitter.com/raffi

Reply via email to