Rate Limits for TiLive Recording Bots
Live recording automation needs discipline. Poll too slowly and you miss streams; poll too aggressively and APIs start pushing back.
Separate TiLive checks from Telegram sends
TiLive lookups and Telegram uploads have different limits. A clean architecture keeps separate gates for source checks, bot commands, and outbound messages.
This prevents one busy workflow from starving the rest of the bot.
Deduplicate active recordings
If five users request the same live, the service should run one recording and attach all requesters to it.
That saves CPU, bandwidth, storage, and upload time while keeping the user experience identical.
Use clear failure states
Offline, user-not-found, auth-required, rate-limited, and stream-resolve errors should produce different user messages.
Those distinctions make support much easier and reduce repeated commands from confused users.
Keep watchlist polling steady and let command cooldowns absorb impatient retries.
Open @tiliverec_bot