Taylor, I don't think Twitter should develop its API in accordance with, or let API design decisions be influenced by deficiencies in third-party libraries.
Your API should adhere to specs, and third-party libraries should follow suit. The OAuth spec has said from Version 1: "Parameters are sorted by name, using lexicographical byte value ordering. If two or more parameters share the same name, they are sorted by their value." On Mar 11, 4:27 pm, Taylor Singletary <taylorsinglet...@twitter.com> wrote: > 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 > spec. > > Taylor Singletary > Developer Advocate, Twitterhttp://twitter.com/episod > > 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)