Under the hood
Useful2 Signal3
Cloud sessions can be handed a hook script up front, with a checksum so stale uploads get refused.
What's wrong with this entry?
Anonymous. No account, no email.
What
The protocol between your machine and a cloud session gained an upload step that sends a hook script body (base64, at most 360,000 characters) with a SHA-256 the cloud side checks against its own table, optionally tagged with the worker generation so a stale upload is refused.
Details
- Registration replies now also carry which hook ids were ignored, which templates are held, and an "away since" timestamp set when this machine had been treated as absent after two forwarded hook runs went unanswered.
- Documented refusals: hook forwarding disabled, hook forwarding not ready, stale worker generation, invalid upload, template refused.
Evidence
@internal Success payload answering upload_device_hook_template.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.