Pass errors through better during 1:1 setup
Route direct messages if route exists
Proxy through the registration form and record the route
Change node name for "new Cheogram"
Handle errors from backend gateway

Well, log them for now.  Need to send more data along if we're going to
reflect them back properly.
Some cabal updates
Huge refactor to use seperate backend and some other stuff
Catch more exceptions, print more restart logs!
First explicit signature!
Use log everywhere
Do not notify user on rejoin
No one cares about join/part

SMS users rarely do it, and social cues might be in place to handle that
anyway.  Data users flap way to much to be useful, and usually can read
backscroll anyway so they'll see you message when they come back.

If you really want to see join/part messages, you can explicitly ask for
them, with a set debounce (in seconds)
Debound both joins and parts
Advertise jabber:iq:gateway support
Merge presences into old_presences

In case rejoin attempts happen without a sucessful join in the middle.
Rejoin on status 332

Closes #36
Rejoin even if remote server takes awhile to come back

Make sure that on rejoin we end up with a correct list of who is in the

Almost done #36
Replace startup join logic with constant pings

We might restart, the remote might restart, best way is to just
constantly check if we're still in the room.  On startup, re-check each
of our users and rejoin anyone who does not respond to ping.  Then keep

Partial for #36
Persist rooms we create, allow anyone to send invites

The latter is not supported on Prosody
<https://prosody.im/issues/issue/254> which is why we still set everyone
to owner when inviting.