Upgrade to v0.13.0

conf/app.src

@@ -1,5 +1,5 @@
-SOURCE_URL=https://github.com/mautrix/telegram/archive/refs/tags/v0.12.2.tar.gz
+SOURCE_URL=https://github.com/mautrix/telegram/archive/refs/tags/v0.13.0.tar.gz
-SOURCE_SUM=a25e298db1d0de7113eb6f047e2862fc737c5ee8545473cb7e4fe8b8260eaab9
+SOURCE_SUM=e0848c5042f6cdf3609c31e940503a1e9b3e6510ff327393dfca3b894c4b9caa
 SOURCE_SUM_PRG=sha256sum
 SOURCE_FORMAT=tar.gz
 SOURCE_IN_SUBDIR=true

conf/config.yaml

@@ -21,7 +21,6 @@ homeserver:
   # Whether asynchronous uploads via MSC2246 should be enabled for media.
   # Requires a media repo that supports MSC2246.
   async_media: false
-
 # Application service host/registration related details
 # Changing these values requires regeneration of the registration.
 appservice:
@@ -30,14 +29,12 @@ appservice:
   # When using https:// the TLS certificate and key files for the address.
   tls_cert: false
   tls_key: false
-
   # The hostname and port where this appservice should listen.
   hostname: 0.0.0.0
   port: __PORT__
   # The maximum body size of appservice API requests (from the homeserver) in mebibytes
   # Usually 1 is enough, but on high-traffic bridges you might need to increase this to avoid 413s
   max_body_size: 1
-
   # The full URI to the database. SQLite and Postgres are supported.
   # Format examples:
   #   SQLite:   sqlite:///filename.db
@@ -49,7 +46,6 @@ appservice:
   # For sqlite, min_size is used as the connection thread pool size and max_size is ignored.
   # Additionally, SQLite supports init_commands as an array of SQL queries to run on connect (e.g. to set PRAGMAs).
   database_opts: {}
-
   # Public part of web server for out-of-Matrix interaction with the bridge.
   # Used for things like login if the user wants to make sure the 2FA password isn't stored in
   # the HS database.
@@ -61,7 +57,6 @@ appservice:
     # The base URL where the public-facing endpoints are available. The prefix is not added
     # implicitly.
     external: https://example.com/public
-
   # Provisioning API part of the web server for automated portal creation and fetching information.
   # Used by things like mautrix-manager (https://github.com/tulir/mautrix-manager).
   provisioning:
@@ -72,7 +67,6 @@ appservice:
     # The shared secret to authorize users of the API.
     # Set to "generate" to generate and save a new token.
     shared_secret: generate
-
   # The unique ID of this appservice.
   id: __APPSERVICEID__
   # Username of the appservice bot.
@@ -81,21 +75,17 @@ appservice:
   # to leave display name/avatar as-is.
   bot_displayname: Telegram bridge bot
   bot_avatar: mxc://maunium.net/tJCRmUyJDsgRNgqhOgoiHWbX
-
   # 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
-
   # Authentication tokens for AS <-> HS communication. Autogenerated; do not modify.
   as_token: __AS_TOKEN__
   hs_token: __HS_TOKEN__
-
 # Prometheus telemetry config. Requires prometheus-client to be installed.
 metrics:
   enabled: false
   listen_port: 8000
-
 # Manhole config.
 manhole:
   # Whether or not opening the manhole is allowed.
@@ -106,7 +96,6 @@ manhole:
   # If empty, any UIDs can be specified in the open-manhole command.
   whitelist:
     - 0
-
 # Bridge config
 bridge:
   # Localpart template of MXIDs for Telegram users.
@@ -118,7 +107,6 @@ bridge:
   # Displayname template for Telegram users.
   # {displayname} is replaced with the display name of the Telegram user.
   displayname_template: "{displayname} (Telegram)"
-
   # Set the preferred order of user identifiers which to use in the Matrix puppet display name.
   # In the (hopefully unlikely) scenario that none of the given keys are found, the numeric user
   # ID is used.
@@ -143,7 +131,9 @@ bridge:
   # as there's no way to determine whether an avatar is removed or just hidden from some users. If
   # you're on a single-user instance, this should be safe to enable.
   allow_avatar_remove: false
-
+  # Should contact names and profile pictures be allowed?
+  # This is only safe to enable on single-user instances.
+  allow_contact_info: false
   # Maximum number of members to sync per portal when starting up. Other members will be
   # synced when they send messages. The maximum is 10000, after which the Telegram server
   # will not send any more members.
@@ -303,7 +293,6 @@ bridge:
       # session before changing it. The Matrix spec recommends 100 as the
       # default.
       messages: 100
-
   # Whether or not to explicitly set the avatar and room name for private
   # chat portal rooms. This will be implicitly enabled if encryption.default is true.
   private_chat_portal_meta: false
@@ -312,6 +301,8 @@ bridge:
   delivery_receipts: false
   # Whether or not delivery errors should be reported as messages in the Matrix room.
   delivery_error_reports: false
+  # Should errors in incoming message handling send a message to the Matrix room?
+  incoming_bridge_error_reports: false
   # Whether the bridge should send the message status as a custom com.beeper.message_send_status event.
   message_status_events: false
   # Set this to true to tell the bridge to re-send m.bridge events to all rooms on the next run.
@@ -358,11 +349,9 @@ bridge:
     # 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.
     normal_groups: false
-
     # 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.
     #
     # Using a negative initial limit is not recommended, as it would try to backfill everything in a single batch.
@@ -372,7 +361,6 @@ bridge:
       initial_limit: 10
       # Number of messages to backfill when syncing chats.
       sync_limit: 100
-
     # Settings for incremental backfill of history. These only apply when using MSC2716.
     incremental:
       # Maximum number of messages to backfill per batch.
@@ -391,12 +379,10 @@ bridge:
         supergroup: 10
         # Broadcast channels
         channel: -1
-
   # Overrides for base power levels.
   initial_power_level_overrides:
     user: {}
     group: {}
-
   # Whether to bridge Telegram bot messages as m.notices or m.texts.
   bot_messages_as_notices: true
   bridge_notices:
@@ -406,11 +392,10 @@ bridge:
     # e.g. if bridge_notices.default is false, notices from other users will not be bridged, but
     #      notices from users listed here will be bridged.
     exceptions: []
-
   # An array of possible values for the $distinguisher variable in message formats.
   # Each user gets one of the values here, based on a hash of their user ID.
   # If the array is empty, the $distinguisher variable will also be empty.
-    relay_user_distinguishers: ["🟦", "🟣", "🟩", "⭕️", "🔶", "⬛️", "🔵", "🟢"]
+  relay_user_distinguishers: ["\U0001F7E6", "\U0001F7E3", "\U0001F7E9", "⭕️", "\U0001F536", "⬛️", "\U0001F535", "\U0001F7E2"]
   # The formats to use when sending messages to Telegram via the relay bot.
   # Text msgtypes (m.text, m.notice and m.emote) support HTML, media msgtypes don't.
   #
@@ -436,7 +421,6 @@ bridge:
   #    $username    - Telegram username (may not exist)
   #    $mention     - Telegram @username or displayname mention (depending on which exists)
   emote_format: "* $mention $formatted_body"
-
   # The formats to use when sending state events to Telegram via the relay bot.
   #
   # Variables from `message_formats` that have the `sender_` prefix are available without the prefix.
@@ -447,7 +431,6 @@ bridge:
     join: "$distinguisher <b>$displayname</b> joined the room."
     leave: "$distinguisher <b>$displayname</b> left the room."
     name_change: "$distinguisher <b>$prev_displayname</b> changed their name to $distinguisher <b>$displayname</b>"
-
   # Filter rooms that can/can't be bridged. Can also be managed using the `filter` and
   # `filter-mode` management commands.
   #
@@ -460,10 +443,8 @@ bridge:
     mode: blacklist
     # The list of group/channel IDs to filter.
     list: []
-
   # The prefix for commands. Only required in non-management rooms.
   command_prefix: "!tg"
-
   # Messages sent upon joining a management room.
   # Markdown is supported. The defaults are listed below.
   management_room_text:
@@ -475,10 +456,8 @@ bridge:
     welcome_unconnected: "Use `help` for help or `login` to log in."
     # Optional extra text sent when joining a management room.
     additional_help: ""
-
   # Send each message separately (for readability in some clients)
   management_room_multiple_messages: false
-
   # Permissions for using the bridge.
   # Permitted values:
   #   relaybot - Only use the bridge via the relaybot, no access to commands.
@@ -494,7 +473,6 @@ bridge:
     "*": "relaybot"
     "__BOTUSERS__": "puppeting"
     "__BOTADMIN__": "admin"
-
   # Options related to the message relay Telegram bot.
   relaybot:
     private_chat:
@@ -520,8 +498,7 @@ bridge:
     # Whether or not to ignore incoming events sent by the relay bot.
     ignore_own_incoming_events: true
     # List of usernames/user IDs who are also allowed to use the bot commands.
-        whitelist: []
+    whitelist: {}
-
 # Telegram config
 telegram:
   # Get your own API keys at https://my.telegram.org/apps
@@ -529,13 +506,11 @@ telegram:
   api_hash: __APIHASH__
   # (Optional) Create your own bot at https://t.me/BotFather
   bot_token: __BOTTOKEN__
-
   # Should the bridge request missed updates from Telegram when restarting?
   catch_up: true
   # Should incoming updates be handled sequentially to make sure order is preserved on Matrix?
   sequential_updates: true
   exit_on_update_error: false
-
   # Telethon connection options.
   connection:
     # The timeout in seconds to be used when connecting.
@@ -557,7 +532,6 @@ telegram:
     # is not recommended, since some requests can always trigger a call fail (such as searching
     # for messages).
     request_retries: 5
-
   # Device info sent to Telegram.
   device_info:
     # "auto" = OS name+version.
@@ -568,7 +542,6 @@ telegram:
     app_version: auto
     lang_code: en
     system_lang_code: en
-
   # Custom server to connect to.
   server:
     # Set to true to use these server settings. If false, will automatically
@@ -580,7 +553,6 @@ telegram:
     ip: 149.154.167.40
     # The port to connect to. 443 may not work, 80 is better and both are equally secure.
     port: 80
-
   # Telethon proxy configuration.
   # You must install PySocks from pip for proxies to work.
   proxy:
@@ -594,7 +566,6 @@ telegram:
     # Proxy authentication (optional). Put MTProxy secret in password field.
     username: ""
     password: ""
-
 # Python logging configuration.
 #
 # See section 16.7.2 of the Python documentation for more info:

manifest.json

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