MVP · v12.10.1-wsp.1
> android / telegram fork / proxy
Telegram for Android with TgWsProxy integrated directly into the client.
The project keeps Telegram as close to upstream as possible: TgWsProxy runs behind a localhost proxy, Telegram's tgnet remains untouched, and the integration is applied as a small reproducible overlay.
> approach
The integration deliberately avoids replacing Telegram networking. The current source-level overlay changes only five upstream files and does not modify TMessagesProj/jni/tgnet/.
01 / integration
Telegram-WSP starts tgwsproxy-core locally and configures 127.0.0.1:1443 through Telegram's normal proxy API. Telegram itself does not need to know how the external WebSocket transport is implemented.
02 / branding
UNOFFICIAL FORKTelegram's published requirements ask third-party apps not to use the standard Telegram logo and to avoid presenting themselves as the official app. Telegram-WSP therefore uses its own branding and explicitly identifies itself as unofficial.
Telegram requirements ↗> implemented
The current MVP focuses on the integrated proxy path, reproducible Telegram updates, release integrity and keeping the fork maintainable.
No separate proxy application is required for the normal Telegram-WSP flow.
The embedded runtime listens on 127.0.0.1:1443 and is connected through Telegram's existing proxy API.
The overlay is intentionally narrow to reduce merge conflicts when Telegram publishes a new Android version.
GitHub Actions builds the full APK, signs it with the persistent project key and publishes release metadata and corresponding source.
The client checks GitHub Releases and validates SHA-256, package ID and signing certificate before handing the APK to Android.
A scheduled workflow checks DrKLO/Telegram daily and releases a new WSP build only after the overlay and CI gates succeed.
$ architecture
Telegram remains the application and networking layer. The custom transport is isolated behind its localhost proxy endpoint.
> automation
The pipeline separates upstream detection from user updates so an incompatible Telegram version is never treated as a valid WSP release merely because it exists upstream.
UPSTREAM → WSP
WSP → DEVICE
VERIFIED UPDATEThe updater reads latest.json, checks that the new versionCode is newer, downloads the APK and verifies its digest, package ID and signing certificate. Android still requires the user to confirm installation.
> provenance
The embedded core was extracted from the maintained Android fork, which itself descends from amurcanov's Android wrapper and Flowseal's original TgWsProxy runtime.
$ current_release
Android 5.0+ · unofficial fork · built and distributed through GitHub Releases.