APK versions
APK files are served by the original repository.
SHA-256 checksum
4e143fc20b0df378212b1af0953eca2d58a4a90bd8af27caa1452de50524a7d5SHA-256 checksum
22aa8248225e514ee174cf1674e534539f3392f43e99b181f8f36a91f7990568SHA-256 checksum
7d40bf8bfb11352281fef86b38307c8f9fa349b3fc36597b35616308a9608dc4SHA-256 checksum
19a8ee2d56b8edee86ed76b5e1155c3966db3083ccd0fe400429fca729325ba7SHA-256 checksum
b70794702321026d4873fb2c3581e1df6f1501bfd89ab0e7bbb1ff0d5a802053SHA-256 checksum
9a9cc654a494d688554844b96ab0b80effa6615da7e6ce9065aaf44353866f92SHA-256 checksum
e12db108aeeb4b4ea82c378ab43a283f53787d81a96493a16d79fd935cb66acbSHA-256 checksum
c559207dcdfdc101ba6dc628c6967412d7111b6c5349e476ab9700947de9fc24SHA-256 checksum
cde72baa6a74ee73426ddf0d6707535bed2ebc3d13acec1f08f29a945318963eScreenshots
About this app
Telegram MTProto WebSocket Bridge Proxy — a Rust vibecoded port of Flowseal/tg-ws-proxy. Listens for Telegram Desktop's MTProto connections on a local port and tunnels them through WebSocket (TLS) connections to Telegram's DC servers. Telegram channel: @tgwsproxy_rs. Telegram Desktop → MTProto (TCP 1443) → tg-ws-proxy-rs → WS (TLS 443) → Telegram DC ↘ CF proxy (kws{N}.{cf-domain}) → Telegram DC (WS via Cloudflare) ↘ CF Worker (*.workers.dev) → Telegram DC (TCP tunnel via Cloudflare) ↘ upstream MTProto proxy → Telegram DC (WS fallback) ↘ direct TCP :443 → Telegram DC (last resort) Android app A minimal Jetpack Compose wrapper around the same core the CLI runs. Type the flags you would pass to tg-ws-proxy, tap Start, and when the tg://proxy link appears tap it (or let the app open it) to add the proxy in Telegram. The listen address should be 127.0.0.1 so Telegram on the same phone can connect. Add --secret <32 hex chars> if you want the link to stay the same across restarts. --log-file is ignored; logs go to the on-screen view and logcat (tg-ws-proxy). The default arguments carry --quiet, so the on-screen Log panel stays empty until you remove it. That is the default and not a failed start: drop --quiet (or swap it for --verbose) before tapping Start to see log lines. The tg:// link appears either way — it reaches the UI from the listen callback rather than by scraping the log, so --quiet never hides it.
