HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
TelegramMessenger
MTProxy
C2018–2021
TelegramMessenger / MTProxy

MTProxy

Discover this repository through its Hacker News conversations.

3Distinct people
3Mentions
0Explicit recommenders
6.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year3 dated mentions

Observed mentions: 2018-08-31 19:55:17 UTC to 2021-04-21 09:27:56 UTC.

012018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101

What Hacker News says

3 sources
I've been following the situation in Belarus since last August and it's really terrible. I admire how so many brave people look death in the eye and still fight for freedom. I have friends there and this allowed me to understand that there's so much potential in Belarus -- there are so many talented, intelligent people getting by in this adversarial environment. So sad to see how Lukashenko's kleptocracy regime wasted so many years and chances for a better future for millions of people. Anyway -- you can help! Most of the communication, coordination and crime-documenting happens on Telegram and the regime tries to block access to this information. You can run Telegram Proxy [0][1]. The installation is fairly straightforward, mostly setup and forget. After setup you can register your proxy with MTProxybot [2], so that people can learn abou
Read the rest
t/use your proxy. If you know people there, I also recommend setting up a private proxy just for them (i.e. not registering with [2]) and sharing over private communication channel (e.g. Signal), as the thugs try to block proxies, so it's a cat-and-mouse game. Edit: Added info about MTProxybot. [0] https://core.telegram.org/mtproto/mtproto-transports [1] https://github.com/TelegramMessenger/MTProxy [2] https://t.me/MTProxybot
In Belarusian regime’s thugs shut down Imaguru, the country’s key startup hub
I forgot to mention, Telegram also uses its own URL scheme to pass proxy settings so you can send the link to friends or publish it online and they will only have to click it to start using proxy. No need to dig through the settings and type in complicated IP addresses. The link looks like tg://proxy?arguments Proxy uses MTProto, the same protocol that client uses to talk to the server. It is described here: https://core.telegram.org/mtproto The client connects to the proxy as if it were a server, and proxy just relays encrypted packets to the real server. Also, the client may wrap packets with an obfuscation layer (described below) to prevent signature detection. In exchange, the server tells the client to display a channel of the proxy owner in the contact list while proxy is being used. Proxy source on Github (with Docker image link):
Read the rest
https://github.com/TelegramMessenger/MTProxy Bing-translated Russian article about this proxy: https://www.microsofttranslator.com/bv.aspx?from=&to=en&a=ht... Bing-translated review of methods Telegram uses to bypass filtering by an independent researcher: https://www.microsofttranslator.com/bv.aspx?from=&to=en&a=ht... And a little more on obfuscation: https://blog.susanka.eu/how-telegram-obfuscates-its-mtproto-... This article mentions that Telegram uses modified version of obfuscated2 protocol. To detect it the DPI just needs to decode all packets using AES but that would require a lot of CPU power which ISPs currently don't have. Initially all encrypted packets had fixed length so some ISPs started filtering packets by length (of course accidentally filtering non-Telegram packets too but who cares), and Telegram added random padding to prevent this.
In Russia tries more precise technology to block Telegram messenger

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.