I agree with Isaiah. This is a huge improvement over the current PIN workflow.
When will this roll out? Is there an authorization endpoint we can use now for testing purposes? That would be great. On Dec 10 2009, 8:58 am, Isaiah <supp...@yourhead.com> wrote: > This seems like a dramatic improvement to me. When will Twitter start > rolling out support for this, I'd like to be ready with something on github > for this as soon as it lands. > > Isaiah > > YourHead Software > supp...@yourhead.comhttp://www.yourhead.com > > On Dec 10, 2009, at 5:22 AM, Raffi Krikorian wrote: > > > 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-cre.... > > 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 > >
