By way of introduction to some follow up posts: appliances that require a external computer to make them go are a kind of cyber vulnerability. The utility of the device is dependent on the availability of a working interface and thus on the whims of a third party. If they drop support; if they decide to lock some features behind a paywall;1 if they don't support the app on the platform you use, your device is worthless.
While someone could, in principle, program a new interface there are a number of problems:
- Access to information about the device side of the interface. This stuff is trade secrets, and the holders rarely see it as profitable to share it, even if they are no longer supporting the affected devices.
- Good engineering practce may suggest using a a common code base, but manufacturers are also willing to switch hardaware platfomrs to minimize costs. The result is a lot of diversity even within single product lines, as witnessed by the long running struggle to support various peripheries in the linux kernel.
- Finally there are legal barriers to the "just hack it scheme". In the US, for instance, the DMCA, means that the most trival effort by the manufacture to "protect" their kit makes the hacking job a felenoy. Until the right to repair is legally recognized,2 this multiplies the difficulties improsed by the others.
So here in Casa NoSwampCoolers we have a three part policy:
- No device which requies an account registered with the manufacturer.
- No device which requies an app provided by the manufacture to access it's core function.
- Any device which requires an app to access special features or functions must be explicitly discussed by the grownups prior to purchase.
The second part of this series will address the engineering reasons in favor of "use you device to control it", and the third will look at a solution that lets us have the upsides without the downsides.
1 No names, BMW.
2 I consider that a cause worth my political dollars. Would you care to join me?
No comments:
Post a Comment