Let me get this out of my head - I will never implement it and raise my kids at the same time... The way I would like this to work if for one to generate a key/ password for the application and specify what things it can do (can read my followers but cannot change them, cannot read my email, etc) - and make it revokable. How about overlaying the API with another API? Some trustable entity to store my Twitter password and do all this work of keys/Oauth/ whatever and provide the exact same API that Twitter does, so that interested apps just need to switch to that API to provide the service and no changes are needed. Rafa
On Nov 14, 5:35 pm, Dossy Shiobara <[EMAIL PROTECTED]> wrote: > Jesse Stay wrote: > > > I'm okay with anything - OAuth or not, so long as we're not forced to > > store plain-text credentials. > > I just don't want a user's password. A proxy (API key token, OAuth > secret, whatever) is better, even if it doesn't afford any extra actual > security. > > Users are educated over and over not to give up their password except to > the site that it belongs to. Undoing that by encouraging people to give > up their Twitter password is just so frustrating. > > -- > Dossy Shiobara | [EMAIL PROTECTED] |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)
