This just goes to show how badly suited OAuth is for desktop applications: Basically, what ever you do, you will need to direct your users over to a browser (or embed one) and they'll have to deal with strange "passcodes" or whatever you want to call it.<p>This is much more difficult for a user to understand ("why can I give twitter my password, but in this client here, I have to do this strange dance? What am I supposed to do now?").<p>In most of the client apps, the issue of having to enter your password is a non-issue as there's no need for a third-party to know it.<p>In the case of desktop apps, IMHO, OAuth does nothing but makes the lives of both client developers and users harder.