Module telegram 

Telegram messaging bridge — long-polling getUpdates + REST send.

Lifecycle:

1. TelegramBridge::init_global(config, http) — call once at startup.
2. The poll loop runs in a background tokio task (retries forever).
3. TelegramBridge::get() returns the singleton for HTTP handler use.
4. bridge.send(msg) enqueues a message for the REST client.
5. bridge.health() returns the current connection status.

Modules

poller 🔒

Telegram long-polling loop: getUpdates → dispatch → offset advance; outbound mpsc → REST send. Plays the same role as discord::gateway::run_gateway_loop, but with no session/resume state — long polling has no connection to lose beyond a single HTTP request, so this is a plain retry-forever loop around one HTTP GET.

rest

Telegram Bot API REST client — getUpdates long-polling plus sendMessage/editMessageText for outbound delivery.

types

Telegram Bot API wire types (getUpdates / sendMessage / editMessageText).

Structs

TelegramBridge

TelegramConfig

Statics

GLOBAL_BRIDGE 🔒