Upgrade to v0.15.0

conf/app.src

@@ -1,5 +1,5 @@
-SOURCE_URL=https://github.com/mautrix/telegram/archive/refs/tags/v0.14.2.tar.gz
-SOURCE_SUM=8071beb09970d7a337e1a1f7700ecd3f4ef774ba51f2e7199f0216883f023786
+SOURCE_URL=https://github.com/mautrix/telegram/archive/refs/tags/v0.15.0.tar.gz
+SOURCE_SUM=93060a58be005f441402e569d9ba3ad84bdc51e551a2e2d40b5e7e2b01f2413e
 SOURCE_SUM_PRG=sha256sum
 SOURCE_FORMAT=tar.gz
 SOURCE_IN_SUBDIR=true

conf/config.yaml

@@ -325,6 +325,8 @@ bridge:
   # Disable generating reply fallbacks? Some extremely bad clients still rely on them,
   # but they're being phased out and will be completely removed in the future.
   disable_reply_fallbacks: false
+  # Should cross-chat replies from Telegram be bridged? Most servers and clients don't support this.
+  cross_room_replies: false
   # Whether or not the bridge should send a read receipt from the bridge bot when a message has
   # been sent to Telegram.
   delivery_receipts: false
@@ -360,23 +362,6 @@ bridge:
   backfill:
     # Allow backfilling at all?
     enable: true
-    # Use MSC2716 for backfilling?
-    #
-    # This requires a server with MSC2716 support, which is currently an experimental feature in Synapse.
-    # It can be enabled by setting experimental_features -> msc2716_enabled to true in homeserver.yaml.
-    msc2716: false
-    # Use double puppets for backfilling?
-    #
-    # If using MSC2716, the double puppets must be in the appservice's user ID namespace
-    # (because the bridge can't use the double puppet access token with batch sending).
-    #
-    # Even without MSC2716, bridging old messages with correct timestamps requires the double
-    # puppets to be in an appservice namespace, or the server to be modified to allow
-    # overriding timestamps anyway.
-    #
-    # Also note that adding users to the appservice namespace may have unexpected side effects,
-    # as described in https://docs.mau.fi/bridges/general/double-puppeting.html#appservice-method
-    double_puppet_backfill: false
     # Whether or not to enable backfilling in normal groups.
     # Normal groups have numerous technical problems in Telegram, and backfilling normal groups
     # will likely cause problems if there are multiple Matrix users in the group.
@@ -384,10 +369,9 @@ bridge:
     # If a backfilled chat is older than this number of hours, mark it as read even if it's unread on Telegram.
     # Set to -1 to let any chat be unread.
     unread_hours_threshold: 720
-    # Forward backfilling limits. These apply to both MSC2716 and legacy backfill.
+    # Forward backfilling limits.
     #
     # Using a negative initial limit is not recommended, as it would try to backfill everything in a single batch.
-    # MSC2716 and the incremental settings are meant for backfilling everything incrementally rather than at once.
     forward_limits:
       # Number of messages to backfill immediately after creating a portal.
       initial:
@@ -403,7 +387,7 @@ bridge:
         channel: 100
     # Timeout for forward backfills in seconds. If you have a high limit, you'll have to increase this too.
     forward_timeout: 900
-    # Settings for incremental backfill of history. These only apply when using MSC2716.
+    # Settings for incremental backfill of history. These only apply to Beeper, as upstream abandoned MSC2716.
     incremental:
       # Maximum number of messages to backfill per batch.
       messages_per_batch: 100

manifest.json

@@ -6,7 +6,7 @@
         "en": "Telegram puppeting bridge for Matrix/Synapse",
         "fr": "Passerelle Telegram pour Matrix/Synapse"
     },
-    "version": "0.14.2~ynh1",
+    "version": "0.15.0~ynh1",
     "url": "https://docs.mau.fi/bridges/python/telegram/index.html",
     "upstream": {
         "license": "AGPL-3.0-or-later",