Enable appservice ephemeral events by default

CHANGELOG.md

@@ -47,6 +47,10 @@ Minimum Conduit version remains at 0.4.0.
     is not currently supported in the provisioning API.
 * Removed `plaintext_highlights` config option (the code using it was already
   removed in v0.11.0).
+* Enabled appservice ephemeral events by default for new installations.
+  * Existing bridges can turn it on by enabling `ephemeral_events` and disabling
+    `sync_with_custom_puppets` in the config, then regenerating the registration
+    file.
 * Updated to API layer 143 so that Telegram would send new message types like
   premium stickers to the bridge.
 * Updated Docker image to Alpine 3.16 and made it smaller.

mautrix_telegram/example-config.yaml

@@ -84,7 +84,7 @@ appservice:
     # Whether or not to receive ephemeral events via appservice transactions.
     # Requires MSC2409 support (i.e. Synapse 1.22+).
     # You should disable bridge -> sync_with_custom_puppets when this is enabled.
-    ephemeral_events: false
+    ephemeral_events: true
 
     # Authentication tokens for AS <-> HS communication. Autogenerated; do not modify.
     as_token: "This value is generated when generating the registration"
@@ -182,7 +182,7 @@ bridge:
     public_portals: false
     # Whether or not to use /sync to get presence, read receipts and typing notifications
     # when double puppeting is enabled
-    sync_with_custom_puppets: true
+    sync_with_custom_puppets: false
     # Whether or not to update the m.direct account data event when double puppeting is enabled.
     # Note that updating the m.direct event is not atomic (except with mautrix-asmux)
     # and is therefore prone to race conditions.