Developer notes

These pages were written while the backend moved from Node.js to Go. They record design decisions, edge cases and test evidence for contributors. Some describe intermediate states of the migration; for how 3.0 behaves today, start with the user guides: Install and deploy, Configuration, Features and Architecture.

Note Topic
Go migration status Scope, packaging checks and test evidence gathered before the 3.0 release
Go migration plan Original cutover design and compatibility rules
Core delivery verification Acceptance table for downloads, dedup, queue and access control
tgdl-core (2.x companion) The 2.x Go helper binary that 3.0 replaced
Backups Transport details, TGDB archives, crash recovery
Cluster Pairing, catalog sync and media proxy internals
Dialogs Chat list pagination
History jobs Backfill semantics, bounds and resumption
HTTP policy Proxy trust, HTTPS, CSP, quotas and compression
Monitor maintenance Dialog resync, monitor restart, group refresh
Proxies Telegram proxy routing
Purge Group purge, delete-files and factory reset
Recovery Maintenance recovery page
Rescue mode Retention and source-deletion handling
Stories Stories and the proxy probe
Message links t.me link downloads
Sessions and WebSockets Dashboard session revocation
Audit (v2.0) Security and reliability audit frozen at v2.0
Cluster v2.9 → v2.10 Re-pairing peers after the 2.10 token change

Table of contents