v0.9.0

Changes since v0.9.0-rc3

• Fixed cleaning unidentified rooms (#541)

Changes since v0.8.x

Breaking changes

• Prometheus metric names are now prefixed with bridge_
• An entrypoint script is no longer automatically generated. This won't affect most users, as python -m mautrix_telegram has been the official way to start the bridge for a long time.

Added

• Support for logging in by scanning a QR code from another Telegram client (#399).
• Automatic backfilling of old messages when creating portals (#476).
• Automatic backfilling of missed messages when starting bridge (#477).
• Option to update m.direct list when using double puppeting.
• PNG thumbnails for animated stickers when converted to webm (#467).
• Support for receiving ephemeral events pushed directly with MSC2409 (requires Synapse 1.22 or higher).
• Added retrying message sending if server returns 502

Improved

• Switched end-to-bridge encryption to mautrix-python instead of a hacky matrix-nio solution.
• End-to-bridge encryption no longer requires login_shared_secret, it uses MSC2778 instead (requires Synapse 1.21 or higher).
• The bridge info state event is now updated whenever the chat name or avatar changes.
• Double puppeting is no longer limited to users on the same homeserver as the bridge (#520).
• Delivery receipts are no longer sent in unencrypted private chat portals, as the bridge bot is usually not present in them (#483).
• Using the register command now sends a link to the Telegram terms of service.
• The bridge_connected metric is now only set for users who are logged in.

Fixed

• File captions are now sent as a separate message like photo captions.
• The relaybot no longer drops Telegram messages with commands.
• Bridging events of a user whose power level is malformed (i.e. a string instead of an integer) now works (#526).
• Fixed bug where syncing members sometimes kicked ghosts of users who were actually still in the chat.
• Logging out will now delete private chat portals, instead of only kicking the user and leaving the portal in a broken state (#397).
• Unbridging direct chat portals is now possible (#495).