1,220 karma · joined October 15, 2013
No no, it's going to take our jobs!
/s
If Apple still takes 27%, and are still the only ones who can dictate which apps are allowed to run on iPhones (via reviews or notarization or whatever you wanna call it), then I don't see how they aren't still acting as a rent-seeking Gatekeeper.
This aligns with the companies interests too because after they've built that they'll have somewhere to upload telemetry to.
The presence of a cloud API doesn't rule out a LAN API. The control functions exist regardless, just expose them to both the cloud and on the LAN. You could even use the cloud integration to provision authentication for the LAN API (although I'd much prefer a fully local version personally, but I'll take that compromise).
> That means that the vendor has to implement a cloud API for the majority of users. At that point, it's probably cheaper to only have their app use that cloud API, even if the devices are on the same network and could see each other, simply due to the complexity of switching and maintaining the extra logic.
Yep, that makes sense, still doesn't make having a LAN API for users to play with themselves in any way a problem, the device functions still need code somewhere to run, and exposing that code in two APIs is only marginally more work than once, the bulk of the work is in the endpoints/functions themselves.
You could even simplify the process by only building a local HTTP API, and then contain the functionality that communicates with the cloud in a single binary that just makes local HTTP requests and relays the response to the cloud.
> As much as I'd want a local API and would likely avoid most cloud-only devices that I can't somehow convert, I understand why vendors do it.
I'm not gonna lie or pretend to be naive, I understand as well, it's just that as a developer myself I know how I'd do it to provide both with minimal effort, and when I read articles like these it makes me mad because the engineering effort to get them out of this situation is tiny in comparison to the shitstorm they create by making it a legal issue.
I honestly think there needs to be some piece of regulation written about selling devices that require an online backend, because we've seen time and again how devices become non-functional because the company goes bust. That regulation should stipulate that any cloud-based functionality must be replicatable by a device-owner via local control.
But I appreciate the suggestions!
- Reading information from utility providers which few people are able to measure locally
- You want to integrate with some system which is physically outside your home, like I don't know a smart mailbox if those exist (and god damnit now I want that...)
- You are forced to because the product you have can't be controlled any other way and it's not feasible to replace it
- A locally controllable version of X exists, but it's three times the price of one from vendor Y which requires a cloud integrationLocal API for control, then submit telemetry via the cloud-version of the API they use for the app.
The obvious answer why not is: it enables people like me to just block the telemetry uploads.
But they can't have it both ways then, they can't make inefficient cloud-based control mechanisms, and then complain when people (ab)use them, because the truth is that that will not stop no matter how many cease and desists they send.
Security by obscurity is another phrase for it.
So stop building cloud-only device interaction then... Home Assistant users will take a LAN API over a cloud API any day.
A LAN API should satisfy everyone really, no unnecessarily large bills for the manufacturer, and Home Assistant users can get better/faster integrations with shorter update intervals.
Or, god forbid, contributed to the open source code repository in a way beneficial to all.
Me too, the reason I trust it is that I understand the (really cool) cryptography behind it, and most don't.
Basically, with the right cryptography, my app can prove my license is valid without revealing any PII. Or in the case of eIDAS, binary questions like "is rekoil 18 years or older?".
That said, there are things in the category of surveillance that having it in an app do enable. For this reason I would personally like to require that the implementation of these apps is open source, unfortunately I know there was some resistance on that front with regards to eIDAS...
The EU are fucking killing it these days actually. So happy to see it. We had a scare there with Chat Control 2.0 but thankfully it was shot down, besides that we've gotten GDPR, USB-C charging ports, the Digital Markets Act, eIDAS is coming which looks like it could be pretty great, digital drivers licenses, etc. A lot of good stuff.
What did I miss?
The U7-Pro should be a better choice for most home users.