i do not believe we are deprecating the pin workflow, we are adding
another option.

> Does that mean the PIN work flow  will go away?. The given below approach
> may be fine with console based/browserless apps. But i would still prefer
> the the PIN based workflow for desktop apps (which can invoke browser for
> authentication) as users do not prefer sharing their passwords.
>
>> we're not making any fundamental changes to oauth - your apps should
>> continue to work fine.
>>
>> the changes that we are making involve implementing
>>
>> http://tools.ietf.org/html/draft-dehora-farrell-oauth-accesstoken-creds-00#section-4.
>>  this will allow applications to obtain oauth tokens for a user given
>> the user's username / password.
>>
>> On Thu, Dec 10, 2009 at 1:06 AM, Rich <rhyl...@gmail.com> wrote:
>> > Also if you're going to make changes to oAuth and the way it works
>> > currently... please bear in mind many of us already have production
>> > apps using oAuth.
>> >
>> > Maybe you could move the oAuth to versioning to allow us time to move
>> > to newer methods as and when you release them?
>> >
>> > On Dec 9, 7:46 pm, Duane Roelands <duane.roela...@gmail.com> wrote:
>> >> If we're talking about replacing the "PIN Workflow", then this is a
>> >> good idea.  If we're talking about completely different interfaces for
>> >> web and desktop apps, I can't see how that's an improvement.
>> >>
>> >> Seeing as the Search API is still not in line with the rest of the
>> >> API, does this mean that we're going to have three disparate
>> >> incompatible interfaces to juggle?
>> >>
>> >> How is that an improvement?
>> >
>>
>>
>>
>> --
>> Raffi Krikorian
>> Twitter Platform Team
>> http://twitter.com/raffi
>
>



-- 
Raffi Krikorian
Twitter Platform Team
http://twitter.com/raffi

Reply via email to