|
|
@@ -10,6 +10,17 @@ Highly-opinionated (ex-bullshit-free) MTPROTO proxy for
|
|
10
|
10
|
**If you use v1.0 or upgrade broke you proxy, please read the chapter
|
|
11
|
11
|
[Version 2](#version-2)**
|
|
12
|
12
|
|
|
|
13
|
+If you want to have a proxy that _supports adtag_ (possibility to promote a
|
|
|
14
|
+channel with a special Telegram bot), I recommend to use
|
|
|
15
|
+[telemt](https://github.com/telemt/telemt) project. v1 of mtg supports it
|
|
|
16
|
+but I do not see any reasonable point of using it: adtag requires communication
|
|
|
17
|
+via a fragile set of middle proxies, requires complex setup that must expose
|
|
|
18
|
+a public IPs, has lower bandwidth and latency.
|
|
|
19
|
+
|
|
|
20
|
+~10-20k simultaneous connections, has no user management, but ticks all
|
|
|
21
|
+checkboxes related to its main intent: provide a way to use Telegram.
|
|
|
22
|
+mtg idea is simple: minimal unbloated proxy that can handle a reasonable scale
|
|
|
23
|
+
|
|
13
|
24
|
## Rationale
|
|
14
|
25
|
|
|
15
|
26
|
There are several available proxies for Telegram MTPROTO available. Here
|