IoT devs avoid MQTT and Multicast traffic like the plague.
Comment on AWS crash causes $2,000 Smart Beds to overheat and get stuck upright
sugar_in_your_tea@sh.itjust.works 1 day ago
When AWS went down, users lost access to the app that manages its water-cooled coils, leaving them stuck with whatever setting was last active.
That’s ridiculous. The app should merely talk to the device over wifi, if available. The cloud should only be used to connect from outside the wifi network.
Why is everything so crappy?
mlg@lemmy.world 21 hours ago
Tollana1234567@lemmy.today 20 hours ago
i heard people got locked in, or out of thier house on thier smart"locks", and also ring cameras were affected because the ALARM SOUNDS WOULDNT TURN OFF.
muusemuuse@sh.itjust.works 1 day ago
But even that makes little sense as it should take commands locally and any telemetry should be done after the commands are issued. This method basically says “if we ever miss out on telemetry data, it’s just not worth it to us to give you what you already paid for. “
iAvicenna@lemmy.world 1 day ago
eh perhaps to collect usage data and somehow benefit from it.
rdri@lemmy.world 2 hours ago
Because we have webdevs and think of them as devs. They are not devs. They are mostly idiots.
sugar_in_your_tea@sh.itjust.works 2 hours ago
What do you mean? Webdevs are devs, just within a specific platform. And like any dev, they can suck or be great.
rdri@lemmy.world 1 hour ago
It just so happens that overwhelming amount of them do what they should not do - create actual apps (webapps in reality). We could thank Google or frameworks for this, but ultimately their incompetence leads to situations like this. Webdevs thinking of everything as a platform for their stuff that should be working at all times. If they were actual devs they would build proper native apps, think more about how devices actually supposed to work, and rely on cloud less.
sugar_in_your_tea@sh.itjust.works 2 minutes ago
What’s wrong with webapps?
I get that many could be static pages, but you’re comparing web vs desktop. And in that case, I prefer web most of the time. Why? It works the same everywhere, and I can probably access it just fine on my phone without having to get their mobile app, which probably has fewer features and more telemetry.
Web doesn’t make sense for everything, but it’s far better than desktop apps for relatively simple use cases. If the app isn’t performance sensitive and doesn’t need to store a ton of data, web is my preferred platform, especially since I’m a Linux user and would likely need to run the app through WINE instead.