Thanks for finding that, but twitter still refuses it
basestring:
POSThttp%3A%2F%2Fapi.twitter.com
%2Foauth%2Frequest%5Ftokenoauth_consumer_key%3DdHbWZ6idD9VEuQ5tNUufA%26oauth_nonce%3D6739551275477403%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1275477403%26oauth_version%3D1.0
at 4:22 AM, Arthur Pires arthur...@gmail.com wrote:
Thanks for finding that, but twitter still refuses it
basestring:
POSThttp%3A%2F%2Fapi.twitter.com
%2Foauth%2Frequest%5Ftokenoauth_consumer_key%3DdHbWZ6idD9VEuQ5tNUufA%26oauth_nonce%3D6739551275477403%26oauth_signature_method%3DHMAC-SHA1
After some work (and some help from the group) my implementation works,
but...
The QUEST to get an access token
1. app gets a request token from twitter
2. user clicks a button on the ap
3. app opens a twitter page, user types username/password
4. twitter gives user a PIN
5. user
. If this is the case,
you can make your first API call to
http://api.twitter.com/1/account/verify_credentials.json or .xml, which
will return information you need about the user in a format you can easily
consume.
Taylor
On Wed, Jun 2, 2010 at 1:19 PM, Arthur Pires arthur...@gmail.com wrote
