- Stop blindly retrying send_photo/send_video/send_media_group and MAX
send_message on ambiguous network timeouts - a timeout doesn't prove
the message wasn't delivered, and retrying risked posting duplicates
(observed live: a video posted 3-5x after repeated timeout retries).
- Raise/rework timeouts that were too short for real large-file transfer
speeds: TG media upload timeout, and yt-dlp download now uses stall
detection (killed only on true silence) instead of a flat ceiling that
was cutting off legitimately slow-but-successful video downloads.
- Fix sendRichMessage: ok=true with an unparseable message_id no longer
triggers a fallback send (Telegram already created the message).
- MAX: videos over the documented 250MB cap are now sent as a "watch via
link" note instead of silently failing the upload.
- Add PRAGMA busy_timeout to all DB connections.
- Remove unused MAX_MEDIA_CHANNEL_ID (MAX's /uploads returns a portable
token directly, no staging channel needed, unlike Telegram).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
MAX Bot API has no reaction endpoint (confirmed 404 in production logs),
so drop the dead code path entirely instead of eating a warning every post.
Telegram's setMessageReaction is a real Bot API method (verified against
aiogram 3.21.0, the pinned version) - wire it up as a non-fatal
best-effort call after a successful send, mirroring the same
try/except-and-log pattern MAX already used.
exostring