Merge pull request #62 from telemt/main-emergency

Update README.md
This commit is contained in:
Alexey
2026-02-14 20:36:23 +03:00
committed by GitHub

View File

@@ -3,23 +3,37 @@
**Telemt** is a fast, secure, and feature-rich server written in Rust: it fully implements the official Telegram proxy algo and adds many production-ready improvements such as connection pooling, replay protection, detailed statistics, masking from "prying" eyes **Telemt** is a fast, secure, and feature-rich server written in Rust: it fully implements the official Telegram proxy algo and adds many production-ready improvements such as connection pooling, replay protection, detailed statistics, masking from "prying" eyes
## Emergency ## Emergency
**Важное сообщение для пользователей из России** ### RU
Многие из вас столкнулись с проблемой загрузки медиа из каналов с >100k subs...
Мы работаем над проектом с Нового года и сейчас готовим новый релиз - 1.2 Мы уже знаем о проблеме: она связана с dc=203 - Telegram CDN и сейчас есть подтверждённое исправление...
В нём имплементируется поддержка Middle Proxy Protocol - основного терминатора для Ad Tag: Сейчас оно принимо через добавление в конфиг:
работа над ним идёт с 6 ферваля, а уже 10 февраля произошли "громкие события"... ```toml
[dc_overrides]
"203" = "91.105.192.100:443"
```
Мы работаем над поиском всех адресов для каждого "нестандартного" DC...
Если у вас есть компетенции в асинхронных сетевых приложениях - мы открыты к предложениям и pull requests Фикс вне конфига будет в релизе 2.0.0.2
**Important message for users from Russia** Если у вас есть компетенции в асинхронных сетевых приложениях, анализе трафика, reverse engineering, network forensics - мы открыты к мыслям, предложениям, pull requests
We've been working on the project since December 30 and are currently preparing a new release 1.2 ### EN
Many of you have encountered issues loading media from channels with over 100k subscribers…
It implements support for the Middle Proxy Protocol the primary point for the Ad Tag: Were already aware of the problem: its related to `dc=203` Telegram CDN and we now have a confirmed fix.
development on it started on February 6th, and by February 10th, "big activity" in Russia had already "taken place"...
If you have expertise in asynchronous network applications we are open to ideas and pull requests! Currently, you can apply it by adding the following to your config:
```toml
[dc_overrides]
"203" = "91.105.192.100:443"
```
Were working on identifying all addresses for every “nonstandard” DC…
The fix will be included in release 2.0.0.2, no manual config needed.
If you have expertise in asynchronous network applications, traffic analysis, reverse engineering, or network forensics were open to ideas, suggestions, and pull requests.
# Features # Features
💥 The configuration structure has changed since version 1.1.0.0. change it in your environment! 💥 The configuration structure has changed since version 1.1.0.0. change it in your environment!
@@ -476,4 +490,4 @@ docker run --name telemt --restart unless-stopped \
- Multi-upstream Balancer and Failover - Multi-upstream Balancer and Failover
- Strict FSM per handshake - Strict FSM per handshake
- Session-based Antireplay with Sliding window, non-broking reconnects - Session-based Antireplay with Sliding window, non-broking reconnects
- Web Control: statistic, state of health, latency, client experience... - Web Control: statistic, state of health, latency, client experience...