OAuth process, Twitter, and Readability

Question

From what I can tell, Twitter and Readability differ in the order of the OAuth process. Twitter requires:

1. request_token
2. authorize / authenticate
3. access_token

whilst Readability requires:

1. authorize
2. request_token
3. access_token

Meanwhile, the OAuth spec states that the twitter flow is the correct one. Am I missing something, or has readability got this the wrong way round?

Answer 1

Looking at the Readability documentation, I think they were just lazy in how they wrote it. The request token is useless if you've already authorized, so I believe they just put the URLs in the incorrect order.