7 ms·
To put bluntly, anybody who buys hardware that is inexorably linked to some cloud-crap should be ashamed of themselves and deserve the loss of money as a learni
by tarotuser 4y ago
To put bluntly, anybody who buys hardware that is inexorably linked to some cloud-crap should be ashamed of themselves and deserve the loss of money as a learning experience.
I *only* buy hardware that can be controlled and/or managed locally. Sure, it means some 'cool' gadgets aren't available in my world. But it does mean that what I buy will be supported and will just work.
If that means you buy PoE cameras and get a video storage solution? Well, so be it. That's the cost of doing it yourself, BUT it also means you have your own destiny in your control.
Whereas if you buy cloudcrap, *when* the company decides to alter the deal, you're at their behest. Dont like that? Too fucking bad.
- kbuck 4y agoJust because a device isn't cloud-connected doesn't mean it isn't designed for planned obsolescence. For example, the ongoing cheapening of major appliances, or the DRM applied to printer cartridges and coffee pods. This is a legislation problem IMO: companies need to be held to reasonable expectations when they sell a product. My ink cartridge shouldn't say it's "empty" when the page counter reaches 100 [and it's still actually full]. Neither should cloud devices go to the landfill because the company selling them decided that they don't want to support them anymore. Companies foisting negative externalities on us (like more e-waste) in exchange for more profit are a blight and should be treated (and prevented) as such.
- DyslexicAtheist 4y agofully with you except > because the company selling them decided that they don't want to support them anymore. in IoT for consumer devices companies must ensure that a software is free of security issues. in some cases the support period of 3rd party dependencies is out of control of the vendor. and vendors usually don't control the upstream silicon and firmware. so if an SDK ships an outdated mbedtls and upstream refuses to patch their SDK also downstream will not be able to release a patch. and in that case the law says connectivity needs to be disabled for that appliance. the situation today is that vendors are only starting to realize that this is the future in which they operate. so while the appliance is still operable in a dumb-mode any smart-features will have to be reduced to the max time you can ensure support. while this sounds like pretty normal and sane to most it absolutely isn't how IoT vendors in the past have operated. And i hope the minute RED directive kicks into gear by Aug 2024 consumers will start to sue them into oblivion if a vendor is for some reason unable to ship a security update.
- ninkendo 4y agoIt’s not always clear you’re getting cloudcrap when you buy the product. Sure, you and I can do the research and see that it’s tied to a service that will eventually shut down, but do you expect 100% of people out there to understand this?
- throw_pm23 4y agoAnything with the word "smart" falls under this -- that's a good heuristic that covers a large fraction of cases.
- deleted 4y ago[deleted]
- rzzzt 4y agoTo make matters more complicated, some products start as standalone and get "upgraded" to cloudcrap along the way.
- chrisdalke 4y agoThis feels like a very tech-centric perspective. I agree with you, if you restrict this to the very IT-savvy group, but this shifts the blame away from companies’ bad design/behavior. Most people have no understanding of the difference between a cloud-connected device and one that just uses WiFi or BLE locally to communicate with an app. I’d say if you work for a company that produces this kind of crap IoT, shame on you, and that people in that position should strongly push for the ability to ship with offline-only firmware.
- tarotuser 4y agoWow.. the cognitive dissonance here is staggering. Nowhere did I say "build it yourself". There's plenty of turnkey commercial/industrial solutions that are also plug-n-play. Most even have PoE already built in. The problem with them for end-users: you front-load the cost to initial build. The real problem for users with cloud-crap is that it's exceptionally hard to assess risk with cloud crap. As for me, my simplistic solution is that "cloud = unacceptable risk". But that somehow here has translated to "DIY garage build while etching my own silicon and boards", which totally minimizes what I'm actually saying.
- chrisdalke 4y agoI did not suggest that anyone should DIY their IoT hardware. My point is I don’t find utility in shaming users for buying cheap cloud-based products - the average user doesn’t care or know about the tech choices, they just want to be able to change their light colors, play multi-room audio, etc. Yes, a subset of consumers will find local-based IoT products and vote with their wallets, and there are great companies serving that market (at a premium). However, the financial incentives push most companies to produce WiFi/internet connected crap. It’s clearly cheapest to build on a ESP-type WiFi platform and build a bad cloud app. I think the only way you really stop this is with strong financial penalties via regulation. I’d want two pieces: Fines for cloud exfiltration of analytics or WiFi data beyond the base functionality of an application. Funding for FCC or other organizations to actively investigate reports of this. Fines when companies “remotely” brick IoT products that are EOL by shutting off a cloud API. Something of this type should push companies away from any sort of cloud-based infrastructure because they’d need to maintain it for much longer. (Admittedly not well-informed here and maybe this is in progress already?) I understand your perspective is that we can’t trust the government to properly regulate that, and maybe true. But it’s also unrealistic to expect most users to be well-informed. Even if most adults made that choice you still have a huge market of college students buying cheap crap.
- eropple 4y ago> To put bluntly, anybody who buys hardware that is inexorably linked to some cloud-crap should be ashamed of themselves and deserve the loss of money as a learning experience. This isn't "blunt", this is just cruel. Nobody "deserves" to be the victim of false advertising or broken guarantees, particularly when they can reasonably lack the necessary contextual knowledge to analyze them beyond face value. Most people do not have the time or the aptitude (which is developed through more time) to become a system administrator of nontrivial local computing resources, but still derive significant value from being able to things like remotely viewable cameras. The lady mentioned in the article, the one who owns a pet-boarding kennel a few minutes down the road from her house, has her life materially bettered by being able to access cameras remotely, and her life is not materially bettered by becoming a sysadmin to get that except for the fact that she is downstream of bad actors. The solution to this is not "well, everyone should be a sysadmin". The solution is "make the consequences of being a bad actor so petrifying that companies avoid doing so." Candidly, I echoed a lot of the sentiments of your post when I was younger, more self-absorbed, and more confident of my ability to attain sufficient expertise in all walks of life to never need help. My attitudes changed as I grew older and it became clearer that I was just as fallible as the next person, just on different axes. I hope you get the chance to attain perspective, too. We are, as it happens, all in it together, and the attitude your post expresses is counterproductive.
- sircastor 4y agoFor a while I ran DDWRT on my routers, and spent hours learning about FreeNAS and ZFS. And I ran out of patience for it after a few years. I had more important things to do, and people to spend time with. My routers got replaced with Eeros and my NAS got replaced with a Synology. And while I don’t love that the former got bought by Amazon, both are pain free, and I spend a lot less time on them.
- eropple 4y agoYup. Even as a power user there's only so much time in the day. I ran a UniFi network locally for a while, because I was generally frustrated with the state of things. I still have the USG at the top of my network but everything south of it has been replaced with Eeros for Wi-Fi, and they just work(tm). I don't have time to fight with that stuff. I have a life. I still run a FreeNAS box (well, TrueNAS), because I have work-related needs that Synology can't really handle, but that's a conscious choice and I have the skills necessary both to do it and to know that I need to. Most people do not. And that's okay. They have skills I do not have. Modern society functions on division of labor.
- merpnderp 4y agoHow does the average person go about a non cloud connected router? They barely know what it is, let alone what it means to administrate it over the cloud software. How is this their fault for not being a IT professional capable of understanding a $75 purchase?
- tarotuser 4y ago> How does the average person We're not talking about an average person in this instance. We're talking about a company using video surveillance in watching their business. If it were individuals, I would have a bit more sympathy. But this is this company's livelihood being able to realtime watch remotely their core business. So yeah, they can pony up $500 for a good NVR and PoE cams. That would have saved her sob story.
- manuelabeledo 4y ago> I only buy hardware that can be controlled and/or managed locally. Sure, it means some 'cool' gadgets aren't available in my world. But it does mean that what I buy will be supported and will just work. You are part of a vocal minority. The vast majority of people aren't tech savvy. That's why smartphones are the way they are nowadays.
- GirlFriday 4y agoBut didn’t you just say above that you were “suckered” into buying some cloud crap? My apologies if I’m wrong here …