Thanks Duane for your response. On Thu, Jul 9, 2009 at 8:11 PM, Duane Roelands <duane.roela...@gmail.com>wrote:
> > 1. OAuth allows your user to authenticate without ever exposing his > Twitter credentials to your application. > > 2. OAuth allows a user to revoke your application's access to their > account. > > 3. If you don't use OAuth, tweets posted from your application will > show up as "from API" (I believe). You can't put the name of your > application in there unless you use OAuth. > > 4. Basic Auth will eventually be deprecated. If the first three > reasons don't convince you, you should give this one serious > consideration. :) > > I have some issues with OAuth, but they're minor and hardly > insurmountable. Moreover, if you use a library that handles OAuth for > you, implementing it is not a major endeavor. > > Regards, > --Duane > > On Jul 9, 7:56 am, praveen kumar <praveen.neteli...@gmail.com> wrote: > > Hi, > > > > I would like to develop a tool on Twitter, i have few doubts. Please > > clarify. > > > > 1. What is the use of OAuth authorization ? > > > > 2. From Twitter API we can update tweets without OAuth authorization. Why > > this OAuth authorization? > > > > -- > > > Regards, Praveen Kumar
