I'm confused about the OAuth docs linked to from http://apiwiki.twitter.com/
-- especially these:
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-oauth-request_token
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-oauth-access_token
Both of these link to the OAuth 1.0 spec for a list
If you look at the very top of the 1.0 spec, you will see a yellow box...
This specification was obsoleted by OAuth Core 1.0 Revision
Ahttp://oauth.net/core/1.0a on
June 24th, 2009 to address a session fixation
attackhttp://oauth.net/advisories/2009-1/.
The OAuth Core 1.0 Revision A specification
Yup, I know, that's what I'm asking. Why not link to and tell people to use
1.0a (or the IETF draft) rather than 1.0?
For the record I checked all the other code examples and none of them support
oauth_verifier (some do send oauth_callback with the first request), unless I'm
missing something.
most likely, Twitter has other things to do and updating the API
documentation isn't very high on the list.
Ryan
On Fri, Jan 22, 2010 at 4:40 PM, Marc Hedlund marcprecip...@gmail.comwrote:
Yup, I know, that's what I'm asking. Why not link to and tell people to use
1.0a (or the IETF draft)
http://github.com/abraham/twitteroauth/ supports oauth_varifier.
Abraham
On Fri, Jan 22, 2010 at 13:40, Marc Hedlund marcprecip...@gmail.com wrote:
Yup, I know, that's what I'm asking. Why not link to and tell people to use
1.0a (or the IETF draft) rather than 1.0?
For the record I checked
Ah, sorry, my mistake.
-M
On Jan 22, 2010, at 1:57 PM, Abraham Williams wrote:
http://github.com/abraham/twitteroauth/ supports oauth_varifier.
Abraham
On Fri, Jan 22, 2010 at 13:40, Marc Hedlund marcprecip...@gmail.com wrote:
Yup, I know, that's what I'm asking. Why not link to and
