Thoughts on registration

email verification

Having emails for our users is a good thing. If we don't require that, people doesn't give their email. When they forget their passwords, there is no hope sending them anything. It is a pain in the ass however when one needs to wait for a mail to arrive...

I think that registration should be done this way:

  • the user requests registration (either just from the menu, or is prompted that for some operation he needs to do that)
  • a user name, a real email, a password, and a captcha is to be filled
  • the user is told that the account is created, and is active, but needs to be verified in 24 hours, otherwise the account becomes inactive until verification
  • the user is let to continue his operation from she was distracted with the registration procedure

postponed registration

Articles might require being logged in to make comments (but some articles or journals might allow for anonymous cowards). Even when requiring registration, first the user should let to write the comment in the comment editor box, then click comment posting. Then he needs to reminded to either log in or register. Either one, he needs to be able to post the comment without retyping it after he got a valid user/password pair.


Thiblo is going to be a journal factory, where people can create and copy journals. They may give some particular look and feel to their journals. Each hosted journal gets the whole page, and shows its own name and design, without "thiblo" and its look and feel even appear on the screen.

Standard web journals usually have some trivial registration/login interface which fits well in their own design. It is hard if even possible to do if we host many very different journals. That means we should try to resort to totally neutral gui for registration, log in, etc. Something like default xul look and feel. We might use a pop-up layer for registration with the actual content behind it darkened with a dark glass. Then the registration wizard can use the native look and feel of the browser/operating system.

The registration procedure must not only be initiatable to work on its own, but it should be possible to hook in into some other system. For example:

when a user wants to make a comment, a big bubble pops up in a layer where she can edit her comment. Then she pushes the commit button, and then, if not logged in, she needs to be presented with the login interface. That login interface is probably best shown in the very same wizard, without popping up an other dialog. So the 2..4 steps of registration should be somehow be capable of infiltrating to the comment editor dialog.