I concur with David on this one. I didn't take the time to verify
this scenario myself, but it does seem like it's a problem. Consider
the following scenario:
1. A user has whitelisted 10+ web applications using their
credentials.
2. The end user has no knowledge of what an access token is or
bump
On Dec 22, 9:31 am, Corey Ballou ball...@gmail.com wrote:
So... did this make it's way to the bug tracker? Is there any
clarification if not?
On Dec 21, 9:37 am, Corey Ballou ball...@gmail.com wrote:
API call:
http://search.twitter.com/search.json?q=ands=keggeocode=35.22708600...
Hi, im trying to get follower ids using user id and when I do that I
get the 401 Unauthorized
uri: /1/followers/ids.json?user_id={user_id}
Twitter::Unauthorized: (401): Unauthorized - This method requires
authentication.
It works fine if I do screenname
uri:
It is reproducible. Just have valid an access token then go through
/oauth/authenticate with force_login=true and hit cancel. The access token
will no longer be valid.
I would not expect hitting cancel to revoke my access token while I would
expect hitting deny to revoke my access token. I feel
I think my problem is a result of :
Warning: The user ids in the Search API are different from those in
the REST API (about the two APIs). This defect is being tracked by
Issue 214. This means that the to_user_id and from_user_id field vary
from the actualy user id on Twitter.com. Applications
