Also, getting this error response, too:

  <error>Invalid oauth_verifier parameter</error>

On 12/2/10 7:25 PM, Dossy Shiobara wrote:
> Getting this error back from Twitter --
> <hash>
> <request>/oauth/access_token?oauth_consumer_key=((elided))&amp;oauth_nonce=((elided))&amp;oauth_signature_method=HMAC-SHA1&amp;oauth_timestamp=1291335791&amp;oauth_token=((elided))&amp;oauth_version=1.0&amp;oauth_signature=((elided))</request>
>   <error>Invalid / expired Token</error>
> </hash>
> This is on newly "Allow"'ed tokens from Twitter's OAuth.  What gives?

Dossy Shiobara              | |
Panoptic Computer Network   |
  "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) 

Twitter developer documentation and resources:
API updates via Twitter:
Issues/Enhancements Tracker:
Change your membership to this group:

Reply via email to