Taylor, allow me to get on my soapbox again and recommend that Twitter start developing open source client libraries for the API, using the *proven* technologies of C/C++ (gcc for everything except Windows, Microsoft's compilers for Windows) and SWIG. This would neatly solve nearly all "libraries out there not to spec" problems and simplify tremendously the lives of those of us who work with scripting languages.

And it's not just the biggies you get this way - not just Ruby, Perl, Python and PHP. You get at least one version of Lisp and Scheme, though I forget which. You get Java. You get Lua. You even get R and Pike. I haven't looked recently, but I'm guessing there's at least some way of getting all this magic to work on .NET / Mono as well.
M. Edward (Ed) Borasky

"A mathematician is a device for turning coffee into theorems." ~ Paul Erdos

Quoting Taylor Singletary <taylorsinglet...@twitter.com>:

It wasn't a factor in this particular design decision, but the reality
is that the vast majority of OAuth libraries out there are not to

Taylor Singletary
Developer Advocate, Twitter

On Thu, Mar 11, 2010 at 12:06 PM, Dossy Shiobara <do...@panoptic.com> wrote:
So, poor OAuth implementations are forcing a poor technical design
decision in Twitter's product?

Tread carefully ...

On 3/11/10 1:38 PM, Taylor Singletary wrote:
While it's a standard to use multiple values for the same key in this
way, there are a gigantic amount of OAuth libraries out there that
don't account for it and will botch the request as a result.

Dossy Shiobara              | do...@panoptic.com | http://dossy.org/
Panoptic Computer Network   | http://panoptic.com/
 "He realized the fastest way to change is to laugh at your own
   folly -- then you can let go and quickly move on." (p. 70)

Reply via email to