Refactored Handlers to give a nicer external interface/module structure
Moved login/logout handlers to a sperate module
Wrapped the site in a session handler to update expirytimes. Potentially could cause performance issues in the future but is a much better interface.
types and function for the existence of discussions in place.  next step is to somehow get adding and showing them into the interface
adding some display code for discussions
starting handler for discussion view
Added handlers to view and add discussions, wrote the functions to add discussions to documents and comments.  Still debugging - not much UI yet
Work on threaded discussions.

Good test on top-level comments. But sub-comments aren't rendering.
I'm not handling the recursive templating stuff right.
WORK TOWARDS HIERARCHICAL TEMPLATE IN DISCUSSION

I was there, had it working by some weird hackish
method.  Didn't commit.  Tried to rework things
properly, and then found I couldn't get back to
the place where I was before.

Fairly confused by all the type synonyms, but
feel like I'm making some progress.
(HeistT n n Template) is (Splice) is (SnapletISplice App)
(Splices m) is (Splices (SnapletISplice App))
roughly.

Avoiding type errors means not putting a singular in
a plural's place, wrt. Splice vs. Splices.
FIX DISPLAY OF THREADED COMMENTS

Finally got the types figured out well enough to draw
threaded comments hierarchically.  Sweet.  Next I will
tweak the display to make it look a little better, then
I'll try to add the UI elements that allow addition of
comments (that could be pretty hard).
START TRYING DIGESTIVE FUNCTORS FOR DISCUSSION HANDLING

So far not sure if it will fit, because there are so many different
forms on each page..
GET SHOWING AND HIDING OF ADD-DISCUSSION-BOXs
WORKING THREADED DISCUSSIONS
TWEAK DISCUSSION APPEARANCE.  BUGFIX POSTER-ID.
More visual tweaks.  Remove debugging print
NO LONGER BREAK USERNAME ON SPACE. SPACES IN USERNAMES ALLOWED
ADD LINKS FROM DOCUMENT AND COMMENTS TO DISCUSSIONS
SHOW REPUTATION

Showing reputation dirtied the code in two ways.

 * Every page with the standard top navbar had to have its handler
   modified to take the User and all Documents, in order to compute
   the logged-in user's reputation.  That caused a lot of duplicated
   code to show up, when it should probably be handled in a cleaner
   way.

 * Pages that render the username(rep) format (e.g. document
   overviews whose comments are attributed to authors, and the
   author names have rep printed along side) had to have
   the Document map threaded through all the splice-generating
   functions (which can sometimes be ~3 functions deep).  Unclear
   what would be the best way to avoid this.
FIX BUG THAT HIDES FOLLOW BUTTON

Misunderstood some of my code in HandleViewUser - it was meant
to hide the follow button when a user is viewing his/her own
profile.  My last patch hid the follow button whenever the
viewing user was logged in, irrespective of what profile was
being viewed.

This is the fix.
TWEAK UI

Pad discussion point boxes, rearrange wording of author attribution in comments.