[twitter-dev] Re: Handling the OAuth flow when the user clicks Deny / Decline
many thanks - it happens, I guess. On May 7, 7:38 am, Cameron Kaiser wrote: > > You are kidding me? Is my message above reason to Ban me from this > > group? > > I can only conclude this was a mistaken click on somebody's part, so I have > temporarily removed the ban. We'll deal with it off list. > > -- > personal:http://www.cameronkaiser.com/-- > Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com > -- Art is anything you can get away with. -- Marshall McLuhan > -
[twitter-dev] Re: Handling the OAuth flow when the user clicks Deny / Decline
> You are kidding me? Is my message above reason to Ban me from this > group? I can only conclude this was a mistaken click on somebody's part, so I have temporarily removed the ban. We'll deal with it off list. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Art is anything you can get away with. -- Marshall McLuhan -
[twitter-dev] Re: Handling the OAuth flow when the user clicks Deny / Decline
You are kidding me? Is my message above reason to Ban me from this group? On May 6, 4:41 pm, Mobasoft wrote: > Glad that you are finally getting around to this. > I posted it April > 10thhttp://groups.google.com/group/twitter-development-talk/browse_thread... > > On May 6, 10:28 am, jmathai wrote: > > > That would work. So would something a a bit simpler. > > > I am not sure I see the need for the username to be passed back. > > Seems like that could easily be done by the site. Also unsure as to > > why the special key is needed if it's always just returned as a > > parameter. > > > Is this something that can be specified in the OAuth specs? Would be > > nice to have a standard way to handle this very valid OAuth flow. > > > On May 5, 10:36 am, Doug Williams wrote: > > > > I'm trying to decide if this could easily be part of [1]? Any objections > > > for > > > these to be one in the same? > > > > 1.http://code.google.com/p/twitter-api/issues/detail?id=545 > > > > Thanks, > > > Doug > > > -- > > > > Doug Williams > > > Twitter Platform Supporthttp://twitter.com/dougw > > > > On Tue, May 5, 2009 at 8:27 AM, jmathai wrote: > > > > > When the user clicks decline the flow is abruptly disrupted. I didn't > > > > see anything in the OAuth spec that specifies how a "decline" is > > > > handled. > > > > > It would be nice if there was a "decline" url that the application > > > > could specify which the user is redirected to.
[twitter-dev] Re: Handling the OAuth flow when the user clicks Deny / Decline
Glad that you are finally getting around to this. I posted it April 10th http://groups.google.com/group/twitter-development-talk/browse_thread/thread/960612fbcb8059de/5c2231ff33cff9e6?lnk=gst&q=revoke#5c2231ff33cff9e6 On May 6, 10:28 am, jmathai wrote: > That would work. So would something a a bit simpler. > > I am not sure I see the need for the username to be passed back. > Seems like that could easily be done by the site. Also unsure as to > why the special key is needed if it's always just returned as a > parameter. > > Is this something that can be specified in the OAuth specs? Would be > nice to have a standard way to handle this very valid OAuth flow. > > On May 5, 10:36 am, Doug Williams wrote: > > > I'm trying to decide if this could easily be part of [1]? Any objections for > > these to be one in the same? > > > 1.http://code.google.com/p/twitter-api/issues/detail?id=545 > > > Thanks, > > Doug > > -- > > > Doug Williams > > Twitter Platform Supporthttp://twitter.com/dougw > > > On Tue, May 5, 2009 at 8:27 AM, jmathai wrote: > > > > When the user clicks decline the flow is abruptly disrupted. I didn't > > > see anything in the OAuth spec that specifies how a "decline" is > > > handled. > > > > It would be nice if there was a "decline" url that the application > > > could specify which the user is redirected to.
[twitter-dev] Re: Handling the OAuth flow when the user clicks Deny / Decline
That would work. So would something a a bit simpler. I am not sure I see the need for the username to be passed back. Seems like that could easily be done by the site. Also unsure as to why the special key is needed if it's always just returned as a parameter. Is this something that can be specified in the OAuth specs? Would be nice to have a standard way to handle this very valid OAuth flow. On May 5, 10:36 am, Doug Williams wrote: > I'm trying to decide if this could easily be part of [1]? Any objections for > these to be one in the same? > > 1.http://code.google.com/p/twitter-api/issues/detail?id=545 > > Thanks, > Doug > -- > > Doug Williams > Twitter Platform Supporthttp://twitter.com/dougw > > On Tue, May 5, 2009 at 8:27 AM, jmathai wrote: > > > When the user clicks decline the flow is abruptly disrupted. I didn't > > see anything in the OAuth spec that specifies how a "decline" is > > handled. > > > It would be nice if there was a "decline" url that the application > > could specify which the user is redirected to.
[twitter-dev] Re: Handling the OAuth flow when the user clicks Deny / Decline
Doug, I think using the same "URL" would work, but it might be nice to have an extra (or different) param added in order to determine the reason. For example, if a user revokes access from the web and Twitter notifies the "URL", the app may just be updating values in a DB, not displaying anything. Whereas if the user clicks Deny and is sent to the "URL", not only will DB updates be made, but a message provided to the user. Just a thought ;) On May 5, 10:36 am, Doug Williams wrote: > I'm trying to decide if this could easily be part of [1]? Any objections for > these to be one in the same? > > 1.http://code.google.com/p/twitter-api/issues/detail?id=545 > > Thanks, > Doug > -- > > Doug Williams > Twitter Platform Supporthttp://twitter.com/dougw > > On Tue, May 5, 2009 at 8:27 AM, jmathai wrote: > > > When the user clicks decline the flow is abruptly disrupted. I didn't > > see anything in the OAuth spec that specifies how a "decline" is > > handled. > > > It would be nice if there was a "decline" url that the application > > could specify which the user is redirected to. > >
[twitter-dev] Re: Handling the OAuth flow when the user clicks Deny / Decline
I'm trying to decide if this could easily be part of [1]? Any objections for these to be one in the same? 1. http://code.google.com/p/twitter-api/issues/detail?id=545 Thanks, Doug -- Doug Williams Twitter Platform Support http://twitter.com/dougw On Tue, May 5, 2009 at 8:27 AM, jmathai wrote: > > When the user clicks decline the flow is abruptly disrupted. I didn't > see anything in the OAuth spec that specifies how a "decline" is > handled. > > It would be nice if there was a "decline" url that the application > could specify which the user is redirected to. >
