From ef6ad8cfac92a1a9162d90f2ad1db70955114a6c Mon Sep 17 00:00:00 2001 From: Claude Code Date: Mon, 26 Oct 2026 15:17:11 +0100 Subject: [PATCH] mautrix-signal: enable sync_direct_chat_list by default The template still carried false from the pre-bridgev2 configuration. bridgev2's example config and the mautrix-whatsapp role use true. With false, double-puppeted Signal DMs never reach m.direct, so clients list them outside the DM section and do not fall back to the contact's avatar. Refs #5701 --- .../matrix-bridge-mautrix-signal/templates/config.yaml.j2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/custom/matrix-bridge-mautrix-signal/templates/config.yaml.j2 b/roles/custom/matrix-bridge-mautrix-signal/templates/config.yaml.j2 index 884a4b111..3798e0aa8 100644 --- a/roles/custom/matrix-bridge-mautrix-signal/templates/config.yaml.j2 +++ b/roles/custom/matrix-bridge-mautrix-signal/templates/config.yaml.j2 @@ -214,7 +214,7 @@ matrix: # Whether the bridge should send error notices via m.notice events when a message fails to bridge. message_error_notices: true # Whether the bridge should update the m.direct account data event when double puppeting is enabled. - sync_direct_chat_list: false + sync_direct_chat_list: true # Whether created rooms should have federation enabled. If false, created portal rooms # will never be federated. Changing this option requires recreating rooms. federate_rooms: {{ matrix_bridge_mautrix_signal_federate_rooms | to_json }}