Fix Telegram delivery with an authenticated free-tier relay

#1
by Dink0 - opened

Read-only diagnostics show that the bot token, target group and administrator membership work from the owner's Mac, while getMe from the running Space times out after ten seconds. Medialogia ingestion and DeepSeek classification succeed. This proposal adds an optional authenticated Cloudflare Workers Free relay restricted to five Bot API methods and one chat, plus accurate health reporting and independent AI/Telegram workers. Direct Telegram delivery remains the default when relay configuration is absent. No paid host is provisioned. Local Python and Worker checks cover transport selection, authorization, chat/method restrictions, payload limits, rate limits and safe upstream failures. The relay is not yet deployed or verified from HF. The existing Space is intentionally not restarted because its pending SQLite queue is temporary; queue recovery or replay must be addressed before deployment. HF sleeping and queue durability remain separate limitations.

Dink0 changed pull request title from Expose delivery failures and prepare continuous hosting to Fix Telegram delivery with an authenticated free-tier relay

The owner approved updating the temporary queue with replay from Medialogia if needed. Live relay getMe, getChat and getChatMember checks passed. Activating the free-tier relay; original Telegram and DeepSeek secrets are preserved.

Dink0 changed pull request status to merged

Sign up or log in to comment