Here is why I think this *is* in fact useful: When you enter a room that is dark, you look for a light. To turn on this light, you usually look for a switch near this light. Later if you leave this room (and you're aware of green ideas..) you would probably want to turn off this light. Wouldn't you expect to be able to do this by going to that same switch and reverting it back to its previous state?
I do not think it is a good user experience to provide them a means to connect from our site without providing them a means to revoke/remove this connection from the same place. Wouldn't you agree..? -- robbie On Apr 20, 6:36 pm, Abraham Williams <4bra...@gmail.com> wrote: > There is no oauth/revoke method. Personally I don't see much utility in one > except for keeping /settings/connections less cluttered. > > Abraham > > > > > > On Tue, Apr 20, 2010 at 18:15, Robbie Coleman <rob...@gravity.com> wrote: > > I do not see it documented, and dev.twitter.com/doc is throwing 403's on > > searches, but I do see that your own " > >http://twitter.com/settings/connections" "Revoke Access" links call this > > on the click event. > > > I am trying to provide our users a clean UI for managing all of their OAuth > > enabled networks/sites, and twitter is one of those. Both Facebook and > > Google (their OAuth contact API) provide API calls to revoke a user's > > access_token/session_key. > > > Thanks, > > Robbie Coleman > > Software Cleric & Social Shaman > > Gravity > > -- > Abraham Williams | Developer for hire |http://abrah.am > PoseurTech Labs | Projects |http://labs.poseurtech.com > This email is: [ ] shareable [x] ask first [ ] private. > > -- > Subscription > settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en