I agree, in general, however the only reason I brought it up as scope is so that it could serve both apps and twitter. This method would produce for twitter a bad-list in general. But thanks
On Thu, Apr 9, 2009 at 2:13 PM, Brian Gilham <bgil...@gmail.com> wrote: > That's what I had in mind, just to clarify. > -----Original Message----- > From: Mobasoft <mobat...@gmail.com> > > Date: Thu, 9 Apr 2009 14:11:18 > To: Twitter Development Talk<twitter-development-talk@googlegroups.com> > Subject: [twitter-dev] Re: oAuth - App Revoke User Access > > > > IMHO, That is beyond the scope of OAuth. > > Your app should contain/maintain the logic for who is allowed in or in > this case, kept out. > > It is foreseeable that having an OAuth API call to revoke your > application from the user (on their behalf, if you had read/write > access) could be a good thing to have. > > > > On Apr 9, 2:17 pm, Dossy Shiobara <do...@panoptic.com> wrote: > > On 4/9/09 3:14 PM, Peter Denton wrote: > > > > > An App should be able to revoke User access. > > > > Sure, just store a boolean in your app with the OAuth token as to > > whether they're allowed to use your app or not. > > > > -- > > Dossy Shiobara | do...@panoptic.com |http://dossy.org/ > > Panoptic Computer Network |http://panoptic.com/ > > "He realized the fastest way to change is to laugh at your own > > folly -- then you can let go and quickly move on." (p. 70) > -- Peter M. Denton www.twibs.com i...@twibs.com Twibs makes Top 20 apps on Twitter - http://tinyurl.com/bopu6c
