allow unary operations.
hello, babl.

babbling: the basics.
extract broadcasting into a separate function.
send a message on disconnect of users.
display the unhandled message along with the type.

for debugging.
send a connect message as well.

and shorten those things.
add the simplest archiver possible.
load the history on initial load.

inefficiently as well, but we've got no api yet, so it's probably ok.
maybe per-date would be a nice compromise? but that would potentially
mean lots of requests for going back through time, so an api would be
nicer.

it could even work with daily files, reading them into memory (potential
oops) and then serving ranges of dates. hm...