4 ms·
Allow, but.. Username should an arbitrary object-id, service generated. This is OOD, isn't it ? Additionaly user should be given the possibility (not obligat
by jhrobert 19y ago
Allow, but..
Username should an arbitrary object-id, service generated.
This is OOD, isn't it ?
Additionaly user should be given the possibility (not obligation) to provide:
- one or more email addresses (primary & secondaries)
- a unique user chosen ID - 30 or so chars.
- a user chosen Display Name, not unique
- a password (optional too)
User should be able to login using their optional password and either :
- an email address or
- their user chosen unique ID or
- their system generated unique ID
If login fails because user is not known, user should be directed to a pre-filled "register" page ! Never ask user to re-enter data just typed a page before.
Only the object-id and Display Name should be public by default. Display Name should default to unique user, name part of email address or Anonymous.
There should be a log of failed & successful logins, with optional email delivery/alerts.
- jhrobert 19y agoAdditionaly : User should be able to use their email address for password, if they wants it that way. In that case I guess that they should be warned when they allow their email address to be seen by others...
- ralph 19y agoHow do you cope with many users having the Display Name "pg"? How can a reader easily tell which pg it is?