Releases: mautrix/telegram
Releases · mautrix/telegram
v0.2.0-rc6
- Added warning about
delete-portal
kicking all room members - Fixed error when upgrading/creating SQLite database.
v0.2.0-rc5
- Fixed relaybot automatically creating portal rooms when invited to Telegram chat (#145).
- Fixed kicking Telegram puppets and fix error message when bridging chats you've left.
- Fixed integrity error deleting portals from database.
v0.2.0-rc4
FixedAdded Postgres compatibility.- Fixed manual bridging (
!tg bridge
) for unauthenticated users. - Fixed inviting unauthenticated Matrix users from Telegram (via
/invite <mxid>
). - Changed Alembic to read database path from the config, so editing
alembic.ini
is no longer necessary. Usealembic -x config=/path/to/config.yaml ...
to specify the config path.
v0.2.0-rc3
- Reworked Dockerfile to remove virtualenv and use Alpine packages (#142). This fixes webp->png conversion for stickers.
v0.2.0-rc2
- Added Dockerfile by @jcgruenhage
v0.2.0-rc1
- Added
- Option to exclude telegram chats from being bridged.
- Support for using a relay bot to relay messages for unauthenticated users
- Bridging for message pinning and room mentions/pills.
- Matrix->Telegram sticker bridging.
!command
to/command
conversion at the start of Matrix message text.- Conversion of t.me message links to matrix.to message links
- Timestamp massaging (bridge Telegram timestamps to Matrix)
- Support for out-of-Matrix login (useful if you don't want your 2FA password to be stored in the homeserver)
- Optional HQ gif/video thumbnails using moviepy.
- Option to send bot messages as
m.notice
- Improved deduplication
- Matrix file uploads are now reused if the same Telegram file (e.g. a sticker) is sent multiple times
- Room metadata changes and other non-message actions are now deduplicated
- Improved formatting bridging
- Improved Telegram user display name handling in cases where one or more users have set custom display names for other users.
- Fixed Alembic setup and removed automatic database generation.
- Fixed outgoing message deduplication in cases where message is sent to other clients before responding to the sender.
- Moved mautrix-appservice-python to separate repository.
- Switched to telethon-session-sqlalchemy to have the session databases in the main database.
- Switched to AGPLv3
- Probably a bunch of other stuff I forgot