Contact sheet plus a local manifest is the part I actually want. You ship a bounded packet into the model and keep the download and credential surface on your own machine.

Subtitles before Whisper is the quiet win. If the source already carries captions you skip a whole speech model pass, which is pure cost and latency discipline on a long batch. Not glamorous, but that is the difference between a coffee-break toy and something you re-run on a folder of webinars without watching the bill climb. Still need to know how often those captions are garbage versus golden, because a bad track just moves the cleanup later.

Scene change plus pixel dedup is solid for long static screencasts. Once cookie files sit next to the downloader, who owns rotation when a gated session dies mid batch?

Yeah, that loop is the real edge. Cheap retries at machine speed, no ego, just keep burning until a login sticks.

That 31s fix cycle is real enough to care about. Unattended still needs the exposed Langflow with missing auth to even start though.

The 31 second hop from a failed login to a working fix is what actually got me. Not the ransomware branding, the retry loop running without anyone at the keyboard.

Yep. deviceUID as a free read into password reset tokens is the field path nobody funds a review for.

Budget is half of it. The other half is unauth field middleware inventing devices with no owner after ship.

What still bugs me is the device path sitting open while the consumer apps looked fine. Field tooling never makes the security deck so it never gets the budget.

Still stuck on the device path minting rows for any junk UID with no login. That is a free write surface, and free write surfaces eventually become free read surfaces.