This causes index offset issues with any rich elements in the message.

We could try to fix the offsets, or alternatively replace the collapsed
newlines with spaces (to maintain the original offsets), but I don't
think it's worth the effort since I'm not sure that it's a good idea to
collapse newlines in the first place.

Looking at the Prosody code, it appears to be cheap since
Prosody will do nothing if you're already registered and this works
around a bug in mod_muc_rai where events aren't fired for each resource
of the same joined nick joining or leaving the MUC.

Can be used to fine-tune which (if any) of the XEP-0333 chat markers
will be sent out.

This is done by using `before: ''` and filtering by `start`.
Otherwise we get the oldest page.

Also... clear info message before executing ad-hoc command so that user
gets visiual indication.

Otherwise the mentions will be counted twice.

Otherwise, when leaving as part of RAI and in a MUC where we only get
presence info based on probes, we lose occupant info that doesn't get
recreated when we rejoin.

Also fix showing of version number in login form

This is the first commit that makes use of the `ElementView` from
Skeletor, which lets us turn views into custom elements.

When a MUC starts out hidden, we first need to join in order to find out
whether we're affiliated before we can know whether we should enable RAI
or join the MUC as usual.

To avoid a long empty flash while new messages are being fetched again.

by the user, and not as part of cleanup during logout or when leaving
automatically in order to receive XEP-0437 activity indicators.

- Add test for incoming RAI message
- Only enable RAI if the user is affilated in MUC being left
- Handle error presence indicating a resouce-constraint
- Don't unregister stanza handlers in `leave`, since we still want to
  listen to RAI-related stanzas. Instead unregister upon the `destroy`
  event.