Core Auth Library

[eluser]thody[/eluser]
[quote author="jedd" date="1250277538"]And lo, we come full circle.

I would be unlikely to use a library that assumed the user had an email address, let alone wasted session data space on it.

I think the biggest problem that befell many of the other extant auth libraries is that they were coded, in some cases by very smart people, without checking what was required by the target audience.

The second problem is that the target audience, if queried, would be unlikely to respond, and if they did, they'd be shown to disagree on pretty much everything.[/quote]

Jedd, I can't imagine a member-based application that doesn't require an email address (pretty vital for password recovery, etc.). Putting it in the session on the other hand probably isn't necessary, and now that you raise the point I'll probably remove it.

I completely agree with the latter part of your statement. Most libraries include many edge cases, which are important to the author, and no one else, which is exactly why I'm trying to keep this as minimal/abstract as possible. I would propose that email is a field that the vast majority of developers would require.