ScreenTinker 15448d1c5d fix(#142): dedup repeated content-ack reports (secondary load) ... device:content-ack logged + emitted every message, so a device repeatedly reporting the same "content <id>: ready" (observed from an older app version) added avoidable load per message. - Suppress identical (device_id, content_id, status) reports within config.contentAckDedupMs (default 10s), modeled on the lastPlayLogAt throttle. A status change has a different key and passes immediately; a fresh report after the window passes too. In-memory, resets on restart. The handler does no DB writes, so this is purely shedding redundant log+emit work. test: integration over a real authenticated device socket — a burst of identical "ready" collapses to one log/emit, a "ready" after the window passes, and a status change is never deduped. Unique PORT (3984). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>		2026-06-27 19:35:04 -05:00
..
dashboardSocket.js	fix(socket): offline debounce + truthful single-device command feedback	2026-05-14 13:11:40 -05:00
deviceSocket.js	fix(#142): dedup repeated content-ack reports (secondary load)	2026-06-27 19:35:04 -05:00
index.js	Initial open source release	2026-04-08 12:14:53 -05:00