GeiserX/Telegram-Archive v7.5.0

v7.5.0 — SOCKS5 Proxy Support

on GitHub

What's New

SOCKS5 Proxy Support (#104)

You can now route all Telegram connections through a SOCKS5 proxy — useful in regions where Telegram is blocked or behind corporate firewalls.

Configuration (all optional):

TELEGRAM_PROXY_TYPE=socks5
TELEGRAM_PROXY_ADDR=127.0.0.1
TELEGRAM_PROXY_PORT=1080
TELEGRAM_PROXY_USERNAME=
TELEGRAM_PROXY_PASSWORD=
TELEGRAM_PROXY_RDNS=false

Proxy support is applied consistently across all code paths: backup, real-time listener, auth setup, and standalone scripts.

Improvements

• Validation hardening: port range (1–65535), username/password pairing, boolean RDNS parsing, and case-insensitive proxy type
• Security: proxy endpoint details logged at DEBUG (not INFO) to avoid exposing infrastructure topology
• Test isolation: proxy integration tests use scoped fixtures instead of global sys.modules mutation
• Dependency: added python-socks[asyncio]>=2.7.1 (required by Telethon for SOCKS5 transport)

Contributors

Thanks to @samnyan for the proxy feature contribution!

What's Changed

• Add Supporters section to README by @GeiserX in #102
• Add Codecov coverage badge to README by @GeiserX in #103
• feat: Add proxy support for telegram client. by @samnyan in #104

New Contributors

• @samnyan made their first contribution in #104

Full Changelog: v7.4.2...v7.5.0