Encrypted messages edited in Matrix are prefixed with an Asterisk in Telegram

[s3lph]

Telegram already marks edited messages as edited. However, if a message in a bridged channel is edited on the Matrix side, for some reason the edited message on the Telegram side now starts with the string * , in addition to the edited marker (see screenshot below).

Expected Behavior

Actual Behavior

(Disregard the timestamp difference)

Steps to Reproduce

1. Set up a bridged channel
2. Write a message in Matrix
3. Look at the sent message in Telegram
4. Edit the message in Matrix
5. Look at the message in Telegram again
6. Note that there's * prepended to the message

[tulir]

Seems to work fine for me, is the bridge up to date?

[s3lph]

I only recently set the bridge up, pip install mautrix-telegram[all]==0.10.0rc1 in a python3.9 venv.

[s3lph]

Config attached: config.yaml

[JuniorJPDJ]

What matrix client are you using?
Can you provide message and edit event json from matrix side?

[s3lph]

Element on Android.

Original message (decrypted):

{
  "type": "m.room.message",
  "content": {
    "msgtype": "m.text",
    "body": "Test",
  },
  "room_id": "REDACTED"
}

Edit event (also decrypted)

{
  "type": "m.room.message",
  "content": {
    "msgtype": "m.text",
    "body": "* This is a Test",
    "m.relates_to": {
      "rel_type": "m.replace",
      "event_id": "REDACTED",
    },
    "m.new_content": {
      "msgtype": "m.text",
      "body": "This is a Test"
    }
  },
  "room_id": "REDACTED"
}

As you can see, the * is added by the client in the body (I assume this is a backward compat feature for clients that don't support editing messages), but the text that's supposed to be used is in m.new_content. I also saw that there is code in mautrix-python to handle this, but I didn't (yet) look too closely at the code.