I'm adding OAuth support to the Twitter addon for the Io programming language.
I'm trying to follow the example on http://dev.twitter.com/pages/auth#auth-request but there are a number of inconsistencies. Reading the OAuth spec http://oauth.net/core/1.0/#encoding_parameters leads me to believe the the base string is composed by joining together the percent-encoded query, oauth and post parameters with &, and then percent encoding the resulting string. However, the example on dev.twitter.com depicts the status post parameter as urlencoded, but then shows it (double) percent encoded in the base string. Are the post parameters urlencoded in the body but then percent encoded in the base string? Are parameters generally percent-encoded twice? Once before joining with & and then once after?
