Brian Suda's dashboard

This page http://tweetcc.com/cc/ has a list of additional licenses, as well, anyone can enter their own text.

As for the Public Domain License, Creative Commons is moving to the new CC Zero! http://creativecommons.org/license/zero which we are happy to be an early adopter of.

@ted, i think adactio DID offer you a solution. Use the ?update= there is no reason you NEED the persons password except for YOUR convince not theirs. You are now in-control of sensitive information!

there have been plenty of examples of people being phished. Quetchup and Plaxo being just two examples. You give them your name and password in good faith and they go and spam your whole address book. There are probably plenty of other examples that have gone UN-noticed as well.

"hello my name is e" is another example of being phished by a company. You gave your twitter name and password to them to allow them to find your social network friends. Behind the scenes they were posting to twitter on your behalf. Just search for "hello my name is e" http://hellomynameise.com/ and you will quickly see how many people got burned by entering their passwords. It could have been MUCH MUCH worse because people are stupid and use the same password for multiple services!

I am concerned that you are so quick to dismiss "benefit out-weighs any perceived harm", isn't just one person's bank account being completely emptied because of password phishing bad enough?

A solution was offered that solves the problem without having to use a password, and infact is ALOT less code to maintain. That should be your benefit! That certainly out-weights the liability of your service, or an evil employee, taking user passwords and exploiting them across the web.