It is also more secure as the user likely uses the same username/password combo on other sites and if someone hacks you the users info is not compromised.
On Thu, Dec 10, 2009 at 21:11, Josh Roesslein <jroessl...@gmail.com> wrote: > By using oauth your application won't break in the future if the user > switches passwords. > Also you don't need to store their password in the plain. You only > hold onto the credentials until > you get the token. Then you can discard them. > > On Thu, Dec 10, 2009 at 7:55 PM, Fauzil Hamdi <asfau...@gmail.com> wrote: > > > > > > 2009/12/10 ryan alford <ryanalford...@gmail.com> > >> > >> Twitter is going to be making changes to OAuth to where the user can > give > >> you their credentials, and you can use those to get an Access Token. > This > >> is an option to bypass the "PIN" workflow. > > > > why use oauth where user can give their credential ? > > > >> > >> On Thu, Dec 10, 2009 at 10:03 AM, Fauzil Hamdi <asfau...@gmail.com> > wrote: > >>> > >>> some body please > >>> > >>> 2009/12/10 Fauzil Hamdi <asfau...@gmail.com> > >>>> > >>>> can i request my mobile application without oauth ? > >>>> my users run away because aouth is not friendly with mobile. > >> > > > > > -- Abraham Williams | Community Evangelist | http://web608.org Project | Intersect | http://intersect.labs.poseurtech.com Hacker | http://abrah.am | http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States
