{"package_name":"io.github.valnesfjord.tgwsproxyrs","name":"TG WS Proxy","summary":"Telegram MTProto WebSocket Bridge Proxy","category":"Connectivity","icon_url":"/api/icon/io.github.valnesfjord.tgwsproxyrs","latest_version_code":205002,"latest_version_name":"2.5.0","apk_url":"/api/apk/io.github.valnesfjord.tgwsproxyrs","apk_size":5193403,"apk_sha256":"50e56055181884316a90b8303adcad215872c2afeb9fd1c0f6f19dd06698b276","source_kind":"fdroid-repo","repo_slug":"fdroid-main","last_updated":1790996419,"release_timestamp":1790962736,"description":"<p><strong>Telegram MTProto WebSocket Bridge Proxy</strong> — a Rust <strong>vibecoded</strong> port of\n<a href=\"https://github.com/Flowseal/tg-ws-proxy\">Flowseal/tg-ws-proxy</a>.</p>\n<p>Listens for Telegram Desktop&#39;s MTProto connections on a local port and\ntunnels them through WebSocket (TLS) connections to Telegram&#39;s DC servers.</p>\n<p>Telegram channel: <a href=\"https://t.me/tg_ws_proxy_rs\">@tg<u>ws</u>proxy_rs</a>.</p>\n<pre><code>Telegram Desktop → MTProto (TCP 1443) → tg-ws-proxy-rs → WS (TLS 443) → Telegram DC\n                                                         ↘ CF proxy (kws{N}.{cf-domain}) → Telegram DC  (WS via Cloudflare)\n                                                         ↘ CF Worker (*.workers.dev) → Telegram DC  (TCP tunnel via Cloudflare)\n                                                         ↘ upstream MTProto proxy → Telegram DC  (WS fallback)\n                                                         ↘ direct TCP :443 → Telegram DC          (last resort)\n</code></pre>\n<h2>Android app</h2>\n<p>A minimal Jetpack Compose wrapper around the same core the CLI runs. Type the\nflags you would pass to <code>tg-ws-proxy</code>, tap <strong>Start</strong>, and when the <code>tg://proxy</code>\nlink appears tap it (or let the app open it) to add the proxy in Telegram.</p>\n<p>The listen address should be <code>127.0.0.1</code> so Telegram on the same phone can\nconnect.</p>\n<p>Add <code>--secret &lt;32 hex chars&gt;</code> if you want the link to stay the same across\nrestarts. <code>--log-file</code> is ignored; logs go to the on-screen view and logcat\n(<code>tg-ws-proxy</code>).</p>\n<p>The default arguments carry <code>--quiet</code>, so the on-screen <strong>Log</strong> panel stays\nempty until you remove it. That is the default and not a failed start: drop\n<code>--quiet</code> (or swap it for <code>--verbose</code>) before tapping <strong>Start</strong> to see log\nlines. The <code>tg://</code> link appears either way — it reaches the UI from th","categories":["Connectivity","Internet","VPN & Proxy"]}