Unfortunately, no. I need to be able to be
sure that there is a one-to-one
relationship between users and
usernames. For example, as far as my
testing has shown, GeekLog would
currently allow situations like this to
1) Student is kicked off GeekLog for good
reasons. Student creates new login
using the same email account.
2) Student is kicked off GeekLog for good
reasons. Student goes to Hotmail.com
and makes a new email address.
Student uses that address to register for
a new GeekLog account.
3) Student is kicked off GeekLog. A friend
allows him/her to use their email
address. That student then registers for
a new account using their friend's email
The way that I see it, I need the following
two things added. I could be wrong, so
please correct me if I overlooked
1) _Only_ <username>
register for GeekLog accounts. All email
addresses that try to register for a
GeekLog account that do not end in this
domain are rejected. (Preferably at the
web interface so that feedback is
2) Only one GeekLog account may be
held by a given email address at a time.
I could see why these would be
configuration options, of course. For out-
of-the-box defaults, GeekLog could use
something like "+\@.+\..+" for account
registration requirements and set the
multiple-accounts-per-email setting on by
default. That will let other GeekLog users
continue to use it without a problem. But I
(and people in my situation) could still
run an effective BBS, intranet, school site,
etc. by changing these variables.
I hope that made sense.