>There are a number of REST API calls that don't require authentication yes, I know :-) Application uses DM - so it must be authenticated.
> But yes, if you do authenticate, use oAuth. it looks curiously - confirm my password usage to myself :-) That is why I'am asking. On Apr 25, 9:51 pm, "M. Edward (Ed) Borasky" <zn...@comcast.net> wrote: > On 04/25/2010 07:50 AM, Abava wrote: > > > For the upcoming basic auth shutdown: > > > What if I have own application that requests data from my own twitter > > account. What is an easiest way for the authentication in this case? > > It is the only one application that works with this account. And it > > works with this account only. Is it still OAuth? > > There are a number of REST API calls that don't require authentication > at all! For example, you can get the list of friends, list of followers > and 16 pages of up to 200 tweets from any non-protected user, including > yourself, without authenticating. The only advantage to authentication > here is that you get the higher oAuth rate limit instead of the default > 150 calls per hour, and the rate limit is assessed per account and not > per IP address. > > But yes, if you do authenticate, use oAuth. > > -- > M. Edward (Ed) Borasky > borasky-research.net/m-edward-ed-borasky > > "A mathematician is a device for turning coffee into theorems." ~ Paul Erdõs > > -- > Subscription > settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en