> don't be evil. in a web scenario, send them to twitter.com for the > oauth workflow. in the case that you can't do that, do not store the > username and password - simply pass them through and store the tokens > instead.
*And* reinforce to users that 3rd party web services should use OAuth, not u/p, and encourage them to use services that use true OAuth so that users agree that those web services offering it offer them value. -- ------------------------------------ personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * [email protected] -- This signature is free of dihydrogen monoxide! Ban it now! www.dhmo.org ----
