Commit History
23 days ago
-
restore: fleet-standard relay-v2.37-fill-span (identical to other 4 Spaces; guestwatch experiment removed)
Verified signature812e0d6 -
remove browser eye (operator request); relay-v2.42-guestwatch-pro
Verified signaturef8d328a -
guestwatch v5: browser eye (relay-v2.41-guestwatch-browser)
Verified signature6a91d9f -
guestwatch v4: professional signed eyes (relay-v2.39-guestwatch-pro)
Verified signaturee3ee752
25 days ago
-
guestwatch: ship guest_probe.py in image (Dockerfile COPY list)
Verified signature510b7b0
27 days ago
-
Exact copy of Reoo88/On @ 826bfe0 (relay-v2.32-gap-filler)
Verified signaturef847423
30 days ago
-
تنبيه بدء البثّ المباشر إلى تيليغرام + حذف الحسابين غير الموجودين
arena- telegram_api: notify_live_start()/notify_targets()/live_start_text() — رسالة باسم المذيع والتاريخ والوقت إلى القناة والحساب الشخصي، مرة لكل بثّ (منع التكرار بـroom_id في السجلّ الدائم)، وأي فشل يُسجَّل ولا يرمي استثناءً. - app.py: خطّاف في حلقة المراقبة قبل أول اتصال بالمصدر + POST /api/telegram/notify-test. - index.html: زرّ تجربة التنبيه وسطر حالة 🔔 في لوحة تيليغرام. - Dockerfile/variables.env: LIVE_NOTIFY=on, LIVE_NOTIFY_TARGETS=both, LIVE_NOTIFY_TEXT. - اختبارات §18 (33) ⇒ 159/159.eef656f -
Split over-limit broadcasts and send them as ONE album
Reooiq96A broadcast longer than the upload ceiling used to retire FAILED and stay on disk. Now it is split without re-encoding (ffmpeg -c copy -f segment, cut at keyframes, so the original quality is preserved bit for bit) into parts of at most ARCHIVE_PART_MB (default: 95% of the current ceiling, i.e. 1900MB local / 47MB public), and the parts are delivered as a single sendMediaGroup album. Order matters: parts are uploaded to the BACKUP chat first, which satisfies the mandatory-backup rule and yields file_ids, then the channel album is composed from those file_ids with no second upload of the data. Album max is 100 items (~190GB locally). Local deletion (original AND every part) still happens only after both deliveries. Resume safety: part_file_ids are persisted after each part, so a failed album step never re-uploads anything. Verified against the real Bot API before coding: sendVideo with a file:// path pushed a 56.7MB part in 2.7s through the local server, and the album key must be 'me…fee6c6c -
V15: replace YouTube archiving with Telegram
Reooiq96- Removed youtube_api.py, youtube_core.py, youtube_archive.py and their tests - Added telegram_api.py (Bot API transport, local-server discovery, chat identity) - Added telegram_archive.py (same queue/join-window/retry engine, Telegram transport) - Primary destination: TELEGRAM_CHAT_ID; backup copy sent by file_id (no second upload) - Local telegram-bot-api (--local) support raises the file cap 50MB -> 2000MB - entrypoint.sh starts the local server when TELEGRAM_API_ID/HASH are present - Dashboard, README, VARIABLES.md, variables.env and deploy script updated - Recorder untouched: TikTok FLV -> mkvmerge -> ffmpeg -c copy -> MP4 - Tests: 57 archive + 9 dashboard regressions passing096481b
-
Create Dockerfile
Verified signatureb1836be