Support replying with an emote

[turt2live]

[t3chguy]

Because no way to fallback it while making it look nice iirc

[lampholder]

Ah yes, I understand this issue. We couldn't simply translate the emote into a sensible fallback, so we skipped it at the time.

What about if we just blindly inserted the display name into the start of the fallback string? Or even just put /me in there?

[t3chguy]

It'd look rather ugly no?

e.g with

{
    "body": "> <@x:riot.ovh> this is a message\n\n/me has replied",
    "format": "org.matrix.custom.html",
    "msgtype": "m.text",
    "formatted_body": "<mx-reply><blockquote><a href=\"https://matrix.to/#/!vfFxDRtZSSdspfTSEr:matrix.org/$15318208921415cHkHd:riot.ovh\">In reply to</a> <a href=\"https://matrix.to/#/@x:riot.ovh\">@x:riot.ovh</a><br>this is a message</blockquote></mx-reply>/me has replied",
    "m.relates_to": {
      "m.in_reply_to": {
        "event_id": "$15318208921415cHkHd:riot.ovh"
      }
    }
  }

Replies DOES support m.emote just fine if you ignore the fallback requirement

[t3chguy]

(keep in mind not all clients show their emotes as * {displayName} {message} so we shouldn't assume they do plus then we can't do disambiguation and the message would have two headings)

[t3chguy]

two names issue: (the latter is correct)

[robintown]

Replying with an emote is a thing nowadays