It won't work anyway, and people get annoyed.

Surprise, surprise

This means a DB query for every inbound message that has a reply tag,
which is probably not expensive enough to be an issue

For some reason, emoji with skintone modifier showed as doubled, a big
one and then a little one.  The span was being set correctly over the
whole thing, and yet this happened.  If we set it to one longer, it
fixes the problem, and in all testing so far doesn't cause any new
problems. I don't love this because it doesn't fully make sense to me,
but it works so I'm putting it in for now.

They're semantic colours like statuses, it makes no sense for them to
follow primary/error

These are command ui images and bob transfers, at the moment

So they don't get blown away if being used, since relatime is a thing

No need to hand-roll everything

Or maybe it will be ones created more than 30 days ago, depending on the
device, but still it means the cache won't grow unbounded and we can
always fetch again if really needed.

By treating the material surface cover as if it were alpha overlaid on
the background. Use the opacity from account settings within reason, but
keep the box visible.

To avoid popping up the conversation again when we've blocked them