// the find
by-sonic/tglock
🔓 Telegram unblock в один клик — обход блокировки через WebSocket-туннель. Без VPN, без серверов, без подписки. Windows / macOS / Linux. Rust + egui.
TGLock is a local SOCKS5 proxy that tunnels Telegram traffic over WebSocket to web.telegram.org, bypassing Russian ISP IP-level throttling without a VPN. It's a single ~6MB Rust binary with an egui GUI, aimed at Russian users whose providers shape Telegram DC IP ranges but don't block the web domain. Narrow scope: it does exactly one thing.
The technical approach is genuinely clever — decoding the MTProto obfuscated2 init packet (AES-256-CTR on the first 64 bytes) to extract the DC number, then routing per-DC to the corresponding kws{dc}.web.telegram.org WebSocket endpoint. This sidesteps IP-based throttling without touching any third-party infrastructure. The LAN-sharing mode (bind to 0.0.0.0 with one checkbox) is a practical quality-of-life feature for households with a always-on desktop. The codebase is apparently ~350 lines total, which means there's very little surface area to audit — and the HABR.md writeup with architecture notes and gotchas (the tokio select! bias issue for WebSocket pings) shows the author actually understands what they built.
The repo is 90% README and practically no source code is visible in the tree — src/main.rs and src/proxy.rs are it. There are no tests, no benchmarks, and no documentation of the proxy.rs internals beyond the README description. The entire value proposition collapses if Roskomnadzor blocks web.telegram.org, which the author acknowledges but dismisses as unlikely — that's a single point of failure with no fallback mechanism in the code. The README is also heavily sponsored by RoseVPN, which is a commercial product the author promotes throughout; the line between 'open source project' and 'lead gen funnel for a paid VPN' is blurry in a way that should give adopters pause.