Katerina Bletsch seeforschauer

How to set up a Telegram Proxy (MTProxy)

This tutorial will teach you how to set up a Telegram MTProxy on an Ubuntu 22.04 sever using AWS Lightsail, although you can use any other Linux distribution and cloud provider.

Using a Telegram proxy is a safe, easy and effective way of overcoming Telegram bans. It's useful, for example, to keep using Telegram under tyrannical regimes, or to circumvent judges' decisions to block Telegram.

Telegram proxies are a built-in feature in all Telegram apps (both mobile and desktop). It allows Telegram users to connect to a proxy in just one or two clicks / taps.

Telegram proxies are safe: Telegram sends messages using their own MTProto secure protocol, and the proxy can only see encrypted traffic – there's no way for a proxy to decrypt the traffic and read the messages. The proxy does not even know which Telegram users are using the proxy, all the proxy sees is just a list of IPs.

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

Clarify and agree on the scope of the system

User cases (description of sequences of events that, taken together, lead to a system doing something useful)
- Who is going to use it?
- How are they going to use it?

	Github - https://github.com/mantyr

	Golang
	https://github.com/mantyr/conf
	- библиотека для удобного доступа к конфигам, поддерживаются ini файлы
	https://github.com/mantyr/images
	- нативная библиотека для ресайза изображений, а так же для накладывания фильтров
	https://github.com/mantyr/startstop
	- библиотека для приостановки горутин и последующего продолжения их работы
	https://github.com/mantyr/metrics

	package main

	import (
	"database/sql"
	"fmt"
	_ "github.com/go-sql-driver/mysql"
	"log"
	)

	const (

	# Start the old vagrant
	$ vagrant init centos-6.3
	$ vagrant up

	# You should see a message like:
	# [default] The guest additions on this VM do not match the install version of
	# VirtualBox! This may cause things such as forwarded ports, shared
	# folders, and more to not work properly. If any of those things fail on
	# this machine, please update the guest additions and repackage the
	# box.

	-- A method to have RETURNING work if you are partitioning data using trigger.
	-- The method to this madness is:
	--
	-- 1) Use the normal trigger mechanism to insert the data into the child tables, but
	-- Instead of the trigger function returning NULL so that the row does not get⋅
	-- inserted into the master table, it returns the row inserted into the child
	-- table
	--
	-- 2) Postgres will insert the new row from the trigger into the master table
	--