" I'll ask them for a username and password, and log them into OAuh
myself without them having to ever see a web browser."

Announcing that your application is doing an end-run around Twitter's
authentication protocols is a great way to get your app shut down.
Also, your application is likely to break if Twitter makes changes to
the OAuth page layout.

I have lots of issues with OAuth, but it's basic premise is sound:
OAuth allows people to use Twitter without giving away their Twitter

On Aug 17, 6:27 am, Chris Babcock <cbabc...@kolonelpanic.org> wrote:
> On Sun, 16 Aug 2009 18:49:49 -0400
> Jason Martin <legos.j...@gmail.com> wrote:
> > On another note, how "Open Source friendly" is OAuth? I'm not sure
> > if people who write open source software want to be giving out their  
> > Consumer Secret key in their source code
> Reasoning from a faulty premise.
> When you know your code is going to be seen you either avoid doing
> stupid things like hard coding credentials or you learn fast that
> configuration data is not code.
> (Now where I did leave my virtual haddock?)
> Chris Babcock

Reply via email to