Room account data events (m.marked_unread, m.tag, com.beeper.mute) set by Matrix users never reach bridge connectors. The handler code exists in portal.go (handleMatrixAccountData for AccountDataMarkedUnread, AccountDataRoomTags, AccountDataBeeperMute) but these events never arrive because Synapse does not include room account data in appservice transactions.
This means features like marking a chat as unread from Element, changing room tags, or muting from the Matrix side are never bridged to the remote network, even though the connector-side handlers (e.g. HandleMarkedUnread, HandleRoomTag, HandleMute) are implemented.
Found while investigating mautrix/whatsapp#891 (marking a chat as unread not being bridged between WhatsApp and Matrix).
I'll open a PR with a fix for this.
Room account data events (m.marked_unread, m.tag, com.beeper.mute) set by Matrix users never reach bridge connectors. The handler code exists in portal.go (handleMatrixAccountData for AccountDataMarkedUnread, AccountDataRoomTags, AccountDataBeeperMute) but these events never arrive because Synapse does not include room account data in appservice transactions.
This means features like marking a chat as unread from Element, changing room tags, or muting from the Matrix side are never bridged to the remote network, even though the connector-side handlers (e.g. HandleMarkedUnread, HandleRoomTag, HandleMute) are implemented.
Found while investigating mautrix/whatsapp#891 (marking a chat as unread not being bridged between WhatsApp and Matrix).
I'll open a PR with a fix for this.