Re: Status of mj2 development?

Erik Pearson wrote:
> 2. extended user information: I would need to have
> real names for each subscriber, and perhaps store
> other information.
>   
Real names are supported now, but storing other information would 
probably require code changes.
> 3. subscription based on master list and site signup
> key (password): The main list would be set up by an
> initial dump of records from an external source, and
> subsequent changes to the master user database would
> all be administrative (could be hand editing a file.)
> But it would be great to have "sub list" subscriptions
> user-driven, with the restriction that only users in
> the master list could subscribe, and also restricted
> by entering a site pass key.
>   
To require a password for every mj_wwwusr page, you'd need to edit the 
table near the beginning of the mj_wwwusr script.
> (This master list is the school registration database,
> and it must be changed over every year.)
>
> 4. Need to be able to search the archives.
>   
Using what search engine?
> 5. Some ui annoyances: 
>   - changing password is too many steps,
Sign in, visit the subscriptions page, type in the new password, and 
press a button;
how would you change that?
If the passwords are derived from an external database, why do you want 
your subscribers to change their passwords?
>  
>   - navigating around and logging in/out is 
> confusing.
>   
How would you improve it?

Michael