The update channel controls behaviour
In July, Meta pushed a mandatory update intended to detect tampering with the capture LED and disable the camera when the light has been covered or destroyed. UploadVR covered the announced tamper detection and what Meta said it would apply to, including hardware already modified in the field.
This is the useful version of an update. A safeguard can reach devices already sold without another purchase. Whether software closes every physical workaround is a separate empirical question. The larger point remains that a server can set the behaviour of a camera on someone's face after purchase, from outside the room.
The version is invisible in the room
A bystander judging a pair of glasses has the model name, if they can identify it, and whatever they last read about it. No version number is legible from two metres. Nothing reveals whether a unit runs last year's build or this week's.
A norm calibrated in March may describe a device that stopped existing in April. The same channel that hardened the LED can extend a capability, on the same schedule and across hardware already in the world. Release notes go to the owner. The people in front of the camera are not on that distribution list.
Capability changes need public notice
An update that changes what a device can do to people who did not buy it warrants public notice written for them, separate from the changelog. A feature that alters the terms of an encounter is more than a product detail.
Detection tools inherit the problem. Identifying a model identifies hardware, not what that unit currently does, and no scanner can read firmware from an advertising packet. The next build can open a gap between the device described by a tool and its behaviour.
Public notice needs to cover additions and removals. Disabling a camera after tampering changes when capture can occur. A new assistant or processing route may expand what the device can do with an encounter. Bystanders need clarity in either case.
A model name stays visible while its software state changes out of sight. That does not make every update harmful. It does mean that policy and public explanation should refer to capabilities and states, rather than an old description of the frame.