Mautrix-telegram

Latest version: v0.15.1

Safety actively analyzes 629723 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 5 of 6

0.5.2

Not secure
* Fixed null `m.relates_to`'s that break Synapse 0.99.5.

0.5.1

Not secure
* Fixed Python 3.5 compatibility.
* Fixed DBMS migration script.

0.5.0

Not secure
* Replaced rawgit with cdnjs in public website as rawgit is deprecated.
* Fixed login command throwing error when web login is enabled.
* Updated telethon-session-sqlalchemy to fix logging into an account on another DC.
* Stopped adding reply fallback to caption when sending caption and image as
separate messages.

rc4 (2019-03-16)

* Added verbose flag to migration script.
* Added pytest setup and some tests (thanks to [V02460] in [290]).
* Fixed scripts (DBMS migration and Telematrix import) not being included in builds.
* Fixed some database problems.
* Removed remaining traces of ORM that might have been the causes of some other
database problems.
* Removed option to use lxml in HTML parsing as it was messing up emoji offset
handling. The new HTML parser supports using the default python HTMLParser
class since 0.5.0rc1, so lxml wasn't really useful anway.

[290]: https://github.com/mautrix/telegram/pull/290

rc3 (2019-02-16)

* Fixed bridging documents without thumbnails to Matrix.
* Added option to set maximum size of image to send to Telegram. Images above
the size limit will be sent as documents without the compression Telegram
applies to images.
* Fixed saving user portals and contacts.
* Added Telegram -> Matrix poll bridging and a command to vote in polls.

rc2 (2019-02-15)

* Added missing future-fstrings comments that caused the bridge to not start on
Python 3.5.
* Fixed handling of document thumbnails.
* Fixed private chat portals failing to be created.
* Made relaybot handle Telegram chat upgrade events.

rc1 (2019-02-14)

Added
* More config options
* Option to to use Telegram test servers.
* Option to disable link previews on Telegram.
* Option to disable startup sync.
* Option to skip deleted members when syncing member lists.
* Option to change number of dialogs to handle in startup sync.
* More commands
* `username` for setting Telegram username.
* `sync-state` for updating Matrix room state cache.
* `matrix-ping` for checking Matrix login status (thanks to [krombel] in [271]).
* `clear-db-cache` for clearing internal database caches.
* `reload-user` for reloading and reconnecting a Telegram user.
* `session` for listing and terminating other Telegram sessions.
* Added argument to `login` to allow admins to log in for other users.
* Added warning when logging in that it grants the bridge full access to the
telegram account.
* Telegram->Matrix bridging:
* Telegram games
* Message pins in normal groups
* Custom message for unsupported media like polls
* Added client ID in logs when making requests to telegram.
* Added handling for Matrix room upgrades.

Improved
* Removed lxml dependency from the new HTML parser and removed the old parser
completely.
* Switched mautrix-appservice-python state store and most mautrix-telegram
tables to SQLAlchemy core. This should speed things up and reduce problems
with the ORM getting stuck.
* `ensure_started` is now only called for logged in users, which should improve
performance for large instances.
* Displayname template extras (e.g. the `(Telegram)` suffix) are now stripped
when mentioning Telegram users with no username.
* Updated Telethon.
* Switched Dockerfile to use setup.py for dependencies to avoid dependency
updates breaking stuff.
* The telematrix import script will now warn about and skip over duplicate portals.
* Relaybot will now be used for users who have logged in, but are not in the chat.

Fixed
* Bug where stickers with an unidentified emoji failed to bridge.
* Invalid letter prefixes in clean-rooms output.
* Messages forwarded from channels showing up as "Unknown source".
* Matrix->Telegram room avatar bridging.

[krombel]: https://github.com/krombel
[271]: https://github.com/mautrix/telegram/pull/271

0.4.0

Not secure
* No changes since rc2.

rc2 (2018-11-15)

* Fixed kicking Telegram puppets from Matrix.

rc1 (2018-11-15)

Added
* Flag to indicate if user can unbridge portal in provisioning API
(thanks to [turt2live] in [225]).
* Option to send captions as second message (replaces option to send caption
in `body`.
* Room-specific settings.

Improved
* (internal) Added type hints everywhere (mostly thanks to [V02460] in [206]).
* Telegram->Matrix formatter now uses `<pre>` tags for multiline code even if
said code was in the telegram equivalent of inline code tags.
* Better bullets and linebreak handling in Matrix->Telegram formatter.
* Logging in will now show your phone number instead of `None` if you don't
have a username.
* Significantly improved performance on high-load instances (t2bot.io) by
moving most used database tables to SQLAlchemy Core.

Fixed
* Bugs that caused database migrations to fail in some cases.
* Editing the config (e.g. whitelisting chats) corrupting the config.
* Negative numbers (chat IDs) in `/connect` of the provisioning API
(thanks to [turt2live] in [223]).
* Relaybot creating portals automatically when receiving message.
* Not being able to use a bridge bot localpart that would also match the puppet
localpart format.
* Matrix login sync failing completely if the homeserver stopped during a sync
response.
* Errors when cleaning rooms.
* Bridging code blocks without a language.
* Error and lost messages when trying to bridge PM from new users in some cases.
* Logging in with an account that someone has already logged in failing
silently and then breaking the bridge.
* Relaybot message when adding/removing Matrix displaynames.

[V02460]: https://github.com/V02460
[206]: https://github.com/mautrix/telegram/pull/206
[223]: https://github.com/mautrix/telegram/pull/223
[225]: https://github.com/mautrix/telegram/pull/225

0.3.0

Not secure
* Added database URI format examples.
* Bumped maximum Telethon version to 1.2, possibly fixing the catch_up option.

rc3 (2018-08-08)

* Improved Telegram message deduplication options.
* Added pre-send message database check for deduplication.
* Made dedup cache queue length configurable.

rc2 (2018-08-06)

* Added option to change max body size for AS API.
* Fixed a minor error regarding power level changes (thanks to [turt2live] in [203]).
* Updated minimum mautrix-appservice version to include some recent bugfixes.

[turt2live]: https://github.com/turt2live
[203]: https://github.com/mautrix/telegram/pull/203

rc1 (2018-08-05)

Added
* Logging in with a bot
(see [docs](https://docs.mau.fi/bridges/python/telegram/authentication.html#bot-token) for usage).
* You can log in with a personal Telegram bot to appear almost like a real
user without logging in with a real Telegram account.
* Replacing your Telegram account's Matrix puppet with your Matrix account
(see [docs](https://docs.mau.fi/bridges/general/double-puppeting.html) for usage).
* Formatting options for relaybot messages.
* Real displaynames are now supported and enabled by default.
* State events (join/leave/name change) can be independently disabled by
setting the format to a blank string.
* New config sections
* Proper log config, including logging to file (by default)
* Proxy support (requires installing PySocks)
* Separate field for appservice address for homeserver
(useful if using a reverse proxy).
* New permission levels to allow initiating bridges without allowing puppeting
and to allow Telegram puppeting without allowing Matrix puppeting.
* Telematrix import script (see [docs](https://docs.mau.fi/bridges/python/telegram/migrating-from-telematrix.html) for usage).
* Provisioning API (see [docs](https://docs.mau.fi/bridges/python/telegram/provisioning-api.html) for more info).
* DBMS migration script (see [docs](https://docs.mau.fi/bridges/python/telegram/dbms-migration.html) for usage).

Improved
* Tabs are now replaced with 4 spaces so that Telegram servers wouldn't change
the message.
* Help page now detects your permissions and only shows commands you can use.
* Moved Matrix state cache to the main database. This means that the
`mx-state.json` file is no longer needed and all non-config data is
stored in the main database.
* Better lxml-based HTML parser for Matrix->Telegram formatting bridging.
lxml is still optional, so the old parser is used as fallback if lxml is not
installed.
* Disabled Telegram->Matrix bridging of messages sent by the relaybot.
Can be re-enabled in config if necessary.

Fixed
* A `ValueError` in some cases when syncing power levels.
* Telegram connections being created for unauthenticated users possibly
triggering spam protection connection delays in the Telegram servers.
* Logging out if a portal had been deleted/unbridged.

0.2.0

Not secure
* No changes since rc6.

rc6 (2018-06-06)

* Added warning about `delete-portal` kicking all room members.
* Fixed error when upgrading/creating SQLite database.

rc5 (2018-06-01)

* 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.

[145]: https://github.com/mautrix/telegram/issues/145

rc4 (2018-05-29)

* ~~Fixed~~ Added 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. Use `alembic -x config=/path/to/config.yaml ...` to
specify the config path.

rc3 (2018-05-25)

* Reworked Dockerfile to remove virtualenv and use Alpine packages (thanks to
[jcgruenhage] in [142]). This fixes webp->png conversion for stickers.

[142]: https://github.com/mautrix/telegram/pull/142

rc2 (2018-05-21)

* Added Dockerfile (thanks to [jcgruenhage] in [136]).

[136]: https://github.com/mautrix/telegram/pull/136
[jcgruenhage]: https://github.com/jcgruenhage

rc1 (2018-05-19)

* 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 license from GPLv3 to AGPLv3
* Probably a bunch of other stuff I forgot

Page 5 of 6

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.