3 ms·
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
by pilif 16y ago
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.
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?").
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.
In the case of desktop apps, IMHO, OAuth does nothing but makes the lives of both client developers and users harder.
- hboon 16y agoThere's XAuth which helps with this issue so that opening a browser is not needed.
- semanticist 16y agoYes, but you need to ask Twitter nicely to see if they'll let you use it.
- hboon 16y agoIt looks like they'll grant it if you have a mobile app. (I do and they did).