If anything goes wrong, we just log.  If app got killed in the middle of
the process, we don't notice.  So now instead we retry after 3 seconds
whenever something goes wrong and we retry when the app comes back to
the home screen if it didn't happen yet.  Still careful to only ever do
it once.

Off by default

When replying to or mentioning a null-thread message, re-use the thread
id of any existing forked thread from a previous reply to that message
if there is one, so that not everyone replying to a null thread message
ends up generating a new thread when most of the time they mean to all
end up in the same new thread.

Of course user may tap thread icon at any time if they actually want a
second fork.

Mentions still do not generate a new thread since their association is
not tracked, but will follow the forked thread if it exists.

To improve performance when pushing the button, don't hit the DB from UI
thread etc.

And add pack as a tag

And also reply to no id just fall back to quote.

In case it is over network, etc

Instead of always using autogenerated colour

When the link is to a media file, just attach it

dotsindicator must have been pulling in some dependency that messed with
the emoji spans

Can happen if splitting a spannable with a span that starts at the
beginning and a delimiter as the first character.

At least show them as a private message from the room, implement full
form-in-message flow later