Actually, since Twitter has said that Basic Auth will eventually go away, OAuth is going to be the only choice for authentication. Twitter has forced the choice by implementing OAuth in the way that they did.
Why should a user who chooses to support open source by using an open- source Twitter client be punished by having to go through extra hoops that users of closed-source clients don't have to endure? Forcing users of open source Twitter clients to register their individual installations as Twitter applications is not a viable solution. Matt Sanford has even said so. No one is asking for "easy". I just want open source Twitter desktop clients to be able to compete with closed-source versions when it comes to security. Right now, that's not possible because of Twitter's implementation of OAuth. Regards, Duane On Jul 1, 11:23 am, Andrew Badera <and...@badera.us> wrote: > But that's the choice you're forced to make by OAuth, not Twitter. And > it is YOUR choice. Personally, I would probably use the conventional > mechanisms of open source: mailing lists, special interest and user > groups. Pound the pavement and promote yourself. Who said it was going > to be "easy"?
