Hi Andrew,

On May 27, 2011, at 7:02 AM, Andrew W. Donoho wrote:

> My question: Am I in error? Does Twitter return a different callback value 
> for the "No, Thanks" case. If not, I humbly request that Twitter add this 
> important, for a better user experience, notification.

We actually do have a simple callback format for when the user denies access. 
It's not an automatic redirect, but we've always provided a link for users back 
into the app.

It works like this:

When a user doesn't click authorize they go to a screen informing them either 
that the application does not have access to their account, or that the 
application *does* still have access to the account (if they choose ‘Cancel’ on 
the `/authenticate` flow for an already authorized, for example.) This callback 
is the same URL as for the success case, but returns without an 
`oauth_verifier` parameter (since there isn't one) and with an additional 
`denied` parameter, in which we pass the value of the `oauth_token` that the 
request was originally made with.

Now, on the cancellation pages as your currently see them there's a link back 
to the app that is neither big enough or obvious enough for users to respond 
to. Therefore, we already have a design tweak implemented for next week that 
makes it a much clearer “Return to {{Application}}” button on the denied and 
cancel screens. Nothing is changing about the callback structure itself, which 
you can already access for testing.

This should keep both ends of the flow hooked into all kinds of apps. As ever, 
let us know if there's ways we can improve it for you; I'm particularly 
interested in suggestions of extra data to send through in that callback to 
improve the feedback in apps.

Thanks,

Ben

--
@benward
Platform Developer, Twitter

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

Reply via email to