Highly opinionated MTPROTO proxy for Telegram
Full Changelog: https://github.com/9seconds/mtg/compare/v2.1.6...v2.1.7
A regular maintenance release for v1. Updates of dependencies, linters and Go to 1.19
Full Changelog: https://github.com/9seconds/mtg/compare/v2.1.5...v2.1.6
A regular maintenance release for v1. Updates of dependencies, linters and Go to 1.18
Full Changelog: https://github.com/9seconds/mtg/compare/v2.1.4...v2.1.5
This is a hotfix release for 2.1.3 that has broken uploads. Highly recommended to update if you used to share images or videos.
Full Changelog: https://github.com/9seconds/mtg/compare/v2.1.3...v2.1.4
This release made 2 major improvements:
I hope, now mtg is on par with official proxy. Another important thing, is that tunning of tcp-buffer size makes no effect. An option is not removed but completely ignored.
Full Changelog: https://github.com/9seconds/mtg/compare/v2.1.2...v2.1.3
This release slightly extends an interface of mtglib.Logger
, adds a new option AllowFallbackOnUnknownDC
and relevant configuration option allow-fallback-on-unknown-dc
.
This option defines how mtg should behave if client requests unknown DC. Each time when client establishes a connection to a proxy, it sends a number of DC that it wants to connect to. This DC defines a number of the cluster: media, messages, channels and so on. But sometimes clients may issue a number mtg knows nothing about. It may be due to the bugs (https://github.com/9seconds/mtg/issues/208) or because new cluster is present but a version of mtg is old enough to know about it. Telegram works in a way that each cluster may server any request (latency is an issue though). So, if you want a media, you can ask for that from messages cluster and vice versa. You'll get a response but with poor performance.
This option defines if mtg should reject unknowns (default behaviour for running with config and inverse for simple-run) or choose any known DC for that.
Full Changelog: https://github.com/9seconds/mtg/compare/v2.1.1...v2.1.2
This release fixes an issue with a poor performance in media download. Also, lint updates, dependency updates and Golang 1.17
A regular maintenance release: