I use both. OAUTH for users to login but I also post to my app's own twitter account and for that I use Basic http auth since the credentials are hardcoded. I would never setup an app that asks for a users password using Basic and strongly encourage others to only use OAUTH. But feel that Basic is ok for the app's developer/maintainer. It might be worth keeping it around for such uses.
On Jun 25, 9:39 pm, whoiskb <[email protected]> wrote: > I am working on a new desktop client and I am currently weighing the > options of using basic auth or Oauth. I like how basic auth keeps > things simple for the user to register an account and since its a > desktop app the credentials are stored on their machine. I am worried > that oAuth is a bit confusing for users and the last thing I want to > do is introduce a hurdle for my users when using the app. > > So a few questions: > > 1. Is the goal to eventually shut off Basic Authentication, or will > it always be around for backwards compatability > 2. Am I not giving users enough credit in knowing and understanding > the pin process? Have devs that have written desktop apps had any > problems with users not understanding the registration process? > > Thanks! > Kevin
