gramps
ec6a5ca466
Creator ruling 2026-11-09: finish the queue before the new features, gold pass always last. **Retired (platform's surface, not ours):** - 34 scheduled streams — YouTube owns scheduling *and* the reminder that makes it worth anything. - 50 publish recording — Studio owns upload (resumable, quota-aware, explains rejections), and an in-app uploader would widen the OAuth consent to whole-channel video management for one convenience. The app adds "Show in folder" instead. **New tasks:** 65 replay clips (the creator-side buffer YouTube does not give you), 66 timed ticker messages, 67 per-event alert videos, 68 edit-while-live + first-run On-Air. **TASK 65 spec** is the interesting one: 15 s is a clip (10/15/20, default 15); the ring holds encrypted *encoded* fragments in RAM — raw 1080p frames would be ~7.4 GB for 15 s — so there is no steady disk write and no crash debris; F10 saves; the replay layer plays once then hides in Live and loops the last 1–3 elsewhere; silent by default; three kept; the layer is excluded from its own clip (hall of mirrors). **TASK 14 gains Branch 3:** mic input gain ahead of the gate (table boom mics fall under it), webcam blank hotkey, opacity/geometry parity with a collapsed Geometry disclosure, Show-in-folder. **Decisions recorded:** the replay-buffer reversal (it was retired in 2022-era reasoning as "different product"; the case for it won), the platform-surface rule, and voice triggering deferred — always- listening in a streaming app hears the game, so the content is its own false-positive source. Queue refactored to 56 lines by archiving completed rows and the superseded surge plan; HANDOFF at 40.
18 lines
932 B
Markdown
18 lines
932 B
Markdown
# TASK 66 — Timed ticker messages (the ticker's real job)
|
|
|
|
> Catalog: [`TASKS.md`](../TASKS.md). Creator idea 2026-11-09.
|
|
|
|
**Problem.** The ticker today is wired to YouTube events that a new streamer will rarely see — no
|
|
memberships, no Super Chats, nothing to tick. A feature that fires twice a year is furniture.
|
|
|
|
**Idea.** Give the ticker its own clock: a list of creator-written messages plus an interval.
|
|
|
|
- Config: interval (minutes) and a list of lines; rotate in order, newest config wins on restart.
|
|
- Example the creator gave: *every 20 minutes, promote the merch channel*.
|
|
- Yields to an alert: an event's own ticker beats a scheduled one, and the clock resumes after.
|
|
- Off by default, one message to start, no randomisation and no scheduling-per-day until asked.
|
|
|
|
**Where:** the ticker section of the alert box properties.
|
|
|
|
**Tests:** interval firing, rotation order, alert pre-emption, persistence across restart.
|