A3M - Account Authentication & Authorization Module

[eluser]gr0uch0mars[/eluser]
OK, now I understand what you meant. That problem would be only in case with Untrusted IDP, because for Trusted IDP it would be necessary for the user to authenticate himself there, and if he's not the owner, no possibility to register in our site. In the other case, an email verification should be advised. That's a problem of security, but I'm focusing on connectivity.

Don't get me wrong neither: I see Usernames could be more intuitive, to users and to developers; but let's be real: email could let us take advantage of Social networks, where people write all their profiles. We can use that to avoid him write a info again, excepting certain cases (email already in database, taken username, untrusted IDP...)

I know it's a complicated, but I'd like to make something that won't be out-of-date in a year, where users profiles (as it seems is gonna happen) goes through Social Networks; they'll have all the profile info. Let's make the visitor enjoy his visit to our web for the content, not for having to rewrite/revalidate/remember data.

EDIT:
I've just read your last post. Of course I'd like to sing up/in with just a click; even just entering your email and the system detecting what kind of email it is automatically, without pressing ANY button. That's my main purpose of this!!! But we need to think of people who don't have email. All situations should be taken into account.