[eluser]Peng Kong[/eluser]
[quote author="lsemel" date="1270982275"]Peng, thanks for the quick reply! Thanks for adding the events, that would be really useful. I was about to add that myself, actually, because I need to hook into them on my project.
Unique emails: Having a 1-1 correspondence between emails and accounts, rather than 1-many, is useful in many situations. Here are some use cases:
1) If you ever want to let people enter "Email address or username" to sign in as some sites do.
2) If you are doing something like sucking in people's address book to add those people as friends, it helps if each email corresponds to either zero or one accounts, and not more (otherwise which account do you add as the friend?). Facebook and Twitter probably require unique emails for this reason, and neither forces email verification.
3) On LinkedIn, they require unique emails because they sometimes ask for email addresses to verify you know the person when adding them as a connection.
As far as someone registering with your email, I think that's something users will complain about if it happens, and then the site owner can deal with it on a case by case basis. I don't think it's likely to happen very often.
Even though OpenID saves you from having multiple passwords, it might be a good idea to offer users a "Create A Password on This Site" link instead of "Change Password". Let's say someone first signs in via Facebook, but then later decides they don't want us to have access to their Facebook account anymore but still wants to use the site.[/quote]
yep i agree with most of your points. (tho i think fb does requires email verified before you can start using it.) I look into unique emails. However feel free to run ahead with this as a base and re-purpose it
