You don't *have* to get the PIN, as there are 3 different way of letting the user log in. However, for desktop applications the PIN method is preferred. If possible, however, you could use a custom URL handler on your application (something like myapp://authenticate/<oauth_verifier>) to use the normal OAuth flow on a desktop application.
Tom PS: Your message wasn't very clear so if this isn't an answer to your question, sorry. Please try writing your questions in proper English. Thanks! :-) On 12/25/10 7:19 AM, shiyuan ding wrote: > > ths your reply > I think that when using a client the first time ,we should get the pin > first ,it's not humanity , I just want it to be easily used. > > > > On 12月25日, 上午1时57分, Tom van der Woerdt<i...@tvdw.eu> wrote: >> Yes, you can use the normal OAuth flow which allows you to use a >> redirect URL. Alternatively, you could use the xAuth procedure to >> exchange an username and password for a set of OAuth credentials, >> although this method is a method that should only be used as a last >> resort (like cases where there's no browser available, etc). >> >> Tom >> >> On 12/24/10 10:04 AM, shiyuan ding wrote: >> >>> when we use the oauth api ，we should get a PIN through browser before >>> login， I want to know whether has the api witch give me a signin >>> control that I can skip the getting PIN step。 >> >>> many thanks > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk