ScreenTinker 890ec5790f fix(proof-of-play): throttle play_logs writes to prevent runaway bloat ... A player stuck in a tight loop (playlist with 0-second item durations) fires device:play-event 'play_start' ~3x/sec, inserting a play_logs row each time. Three web players doing this generated ~909k rows (99.9% with duration_sec=0) and grew the prod DB to 265 MB. Throttle proof-of-play inserts to at most one per device per 2s (in-memory lastPlayLogAt map). Skipped cycles create no row; the live dashboard progress event still fires every time, so the UI is unaffected. The play_end UPDATE only closes open rows, so throttling play_start is safe. (Junk rows already pruned in prod: 909k deleted, DB 265 MB -> 9.8 MB.) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>		2026-06-02 09:52:22 -05:00
..
dashboardSocket.js	fix(socket): offline debounce + truthful single-device command feedback	2026-05-14 13:11:40 -05:00
deviceSocket.js	fix(proof-of-play): throttle play_logs writes to prevent runaway bloat	2026-06-02 09:52:22 -05:00
index.js	Initial open source release	2026-04-08 12:14:53 -05:00