On 18 Aug 1998, Jason L Tibbitts III wrote:
> the list. When someone joins a list who is not registered, what should
> happen? There are a couple of choices:
> The user goes on completely unaware of their registration, and no password
> is assigned.
If the idea is to promote the idea of registration, they should be aware.
A password should be assigned (otherwise we run into a whole bunch of
other problems, like how do we assign one later?) and thus, the user has
to be informed of it.
> The user is assigned a password and is told somehow about their
> How do to the latter? I'm leaning toward having it attach a document that
> the site owner chooses with password info to every list-specific welcome
OR -- when the user is registered, by one of the following ways:
1) Joining a list
2) Registering seperately.
They are issued a seperate message. If they did #2 and then do #1, should
the message be resent? It should be an option.
Namely, before subscribed to a list, mj checks to see if the user is
registered. If not, register. If already registered, continue.
As for the passwords:
I'm all for the old (has it changed?) CompuServe method of two words
seperated by a digit or special character/symbol from the digit keys like:
The code placed on this list should be neough to get the two words from a
dictionary file. Even one word is fine, but sometimes the two word
combination makes it even EASIER to remember (go figure...more to remember
actually becomes easier to remember) -- especially if you end up getting
an interesting phrase. In addition, using dictionary files (which should
be site-settable for foreign-language dictionaries, and maybe a sample one
should be included and used by default) makes it easier.
Oh, which reminds me about something for the global database. It should
probably also store the default language for the person.
| Brock Rozen | firstname.lastname@example.org |
From: Jason L Tibbitts III <email@example.com>