not at all. twitter.com is already setup completely for oauth echo. at this point, its just 3rd party providers, and end clients. the @twitterapi team is ready to help out any of those that need help.
On Sat, Apr 24, 2010 at 9:28 PM, Jaanus <jaa...@gmail.com> wrote: > Is there any kind of special involvement needed from you every time > someone wants to do OAuth Echo? I thought I'll make my own server for > my own app for some purpose. Judging by the spec you posted on your > blog a while ago (http://mehack.com/oauth-echo-delegation-in-identity- > verificatio), it does not look like some special Twitter involvement > is needed, as long as I implement all that's needed in my app and > server? > > > J > > > On Apr 24, 5:44 pm, Raffi Krikorian <ra...@twitter.com> wrote: > > hi tom! > > > > i will be sending more info about it - we've been working with yfrog, > > tweetphoto, and twitpic to get their services migrated - they are either > > finished or are nearly there. if there are others that you would like > the > > @twitterapi team involved with to help them get migrated over as well, > then > > feel free to drop me an e-mail asking me. > > > > On Sat, Apr 24, 2010 at 10:48 AM, Thomas Woolway <tswool...@gmail.com > >wrote: > > > > > > > > > > > > > Hi Raffi, > > > > > Great that we've got a date for basic auth deprecation, but is there > any > > > news/timescales on OAuth Echo? We've got nine weeks and counting to get > the > > > spec, get the service providers to implement it, build it into clients > and > > > get our user-bases to upgrade if they want to be able to upload photos > post > > > June 30th. That's easier if you're web based, but not a huge amount of > time > > > if you are desktop or mobile based. > > > > > Thanks, > > > > > Tom > > > > > On Sat, Apr 24, 2010 at 4:49 PM, Raffi Krikorian <ra...@twitter.com > >wrote: > > > > >> there is a really good chance - now that oauth 2.0 has been submitted > as a > > >> drafthttp://tools.ietf.org/html/draft-hammer-oauth2-00, we are going > to > > >> spend some time catching up our oauth 2.0 implementation. at that > point, > > >> we'll evaluate letting it loose. > > > > >> On Sat, Apr 24, 2010 at 8:44 AM, Dewald Pretorius <dpr...@gmail.com > >wrote: > > > > >>> Raffi, that is super awesome. Thank you. > > > > >>> Any chance that you will have OAuth 2.0 in production before then? > > > > >>> On Apr 24, 12:40 pm, Raffi Krikorian <ra...@twitter.com> wrote: > > >>> > hi all. > > > > >>> > you're going to be hearing a lot from me over the next 9 weeks. > our > > >>> plan is > > >>> > to turn off basic authorization on the API by june 30, 2010 -- > > >>> developers > > >>> > will have to switch over to OAuth by that time. between now and > then, > > >>> there > > >>> > will be a *lot* of information coming along with tips on how to use > > >>> OAuth > > >>> > Echo, xAuth, etc. we really want to make this transition as easy > as we > > >>> can > > >>> > for everybody. > > > > >>> > as always, please feel free to reach out to this group, or to > > >>> @twitterapi > > >>> > directly. if you need help remembering the date - > > >>>http://bit.ly/twcountdown > > >>> > . > > > > >>> > -- > > >>> > Raffi Krikorian > > >>> > Twitter Platform Teamhttp://twitter.com/raffi > > > > >>> > -- > > >>> > Subscription settings: > > >>> > http://groups.google.com/group/twitter-development-talk/subscribe?hl=en > > > > >> -- > > >> Raffi Krikorian > > >> Twitter Platform Team > > >>http://twitter.com/raffi > > > > -- > > Raffi Krikorian > > Twitter Platform Teamhttp://twitter.com/raffi > -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
