Two suggestions for improving proxy UX in restricted regions.
1. Compound deep links
Combine tg://proxy and tg://resolve into one URL, so users can connect to a proxy AND open a bot/channel in a single tap.
Proposed URL format:
tg://proxy?server=...&port=...&secret=...&resolve=botname&start=param
User flow:
User opens website → taps single tg:// link → Telegram opens
→ proxy connection dialog appears
→ user confirms → navigates to target username
→ user dismisses → still navigates (may already have connectivity)
This is especially important for users who don't have a proxy yet. A website or landing page can provide a single tg:// redirect link — when the user taps it, Telegram opens and does two things at once: prompts to enable the proxy and navigates to the target username. This way, people in restricted regions who currently have no access to Telegram can get both connectivity and a destination in one action.
2. Proxy pool failover
Let operators define a pool of backup servers via @MTProxybot. Right now, when a proxy gets blocked, the user loses connectivity and has to manually find a new one — which often requires Telegram itself to work.
Operator flow:
Operator → @MTProxyBot → registers primary server
→ adds fallback servers (e.g. 3-5 IPs)
→ all linked under a single proxy URL
→ can add/remove servers at any time
→ changes propagate to all connected users automatically
Client flow:
User connects via proxy link → uses server #1
→ server #1 goes down → client detects timeout
→ silently switches to server #2 → "Connecting..." (1-2 sec)
→ Telegram keeps working
The idea: an operator registers a primary server and a list of fallback servers under a single proxy link. The Telegram client knows about the entire pool. If the current server becomes unreachable, the client silently switches to the next one — the user sees a brief "Connecting..." and Telegram keeps working.
The operator can add or remove servers from the pool at any time via @MTProxybot, and changes propagate to all connected users automatically — no need to redistribute a new link.
Both are small additions that would make a huge difference for users in Russia, Iran, etc.
Two suggestions for improving proxy UX in restricted regions.
1. Compound deep links
Combine tg://proxy and tg://resolve into one URL, so users can connect to a proxy AND open a bot/channel in a single tap.
Proposed URL format:
User flow:
This is especially important for users who don't have a proxy yet. A website or landing page can provide a single tg:// redirect link — when the user taps it, Telegram opens and does two things at once: prompts to enable the proxy and navigates to the target username. This way, people in restricted regions who currently have no access to Telegram can get both connectivity and a destination in one action.
2. Proxy pool failover
Let operators define a pool of backup servers via @MTProxybot. Right now, when a proxy gets blocked, the user loses connectivity and has to manually find a new one — which often requires Telegram itself to work.
Operator flow:
Client flow:
The idea: an operator registers a primary server and a list of fallback servers under a single proxy link. The Telegram client knows about the entire pool. If the current server becomes unreachable, the client silently switches to the next one — the user sees a brief "Connecting..." and Telegram keeps working.
The operator can add or remove servers from the pool at any time via @MTProxybot, and changes propagate to all connected users automatically — no need to redistribute a new link.
Both are small additions that would make a huge difference for users in Russia, Iran, etc.