Live data from Hacker News

Vacuum bricked after user blocks data collection – user mods it to run anyway

tomshardware.com

21–30 of 174 posts

Re: Vacuum bricked after user blocks data collection – user mods it to run anyway

#21

Earlier quoted context omitted.

The business has no right to remotely kill a device purchased by an end user.

You don't own the software on the device, they do. If they choose to revoke that license, that is their choice.

I own the device and all of its storage. The exact state of that storage is my business and precisely no one else's.

Re: Vacuum bricked after user blocks data collection – user mods it to run anyway

#23

"From there, he built a Raspberry Pi joystick to manually drive the vacuum, proving that there was nothing wrong with the hardware." He should make these and sell them. It would be worth it to just drive it in "discovery" mode and give it the exact path to follow while cleaning. The constant inability to learn the floor plan is beyond annoying.

Depending on where he lives this might be illegal. Yes, we live in a cyberpunk dystopia where the manufacturer can break what you bought and then send you to jail for repairing it. You can read more about it here: https://consumerrights.wiki/w/Digital_Millennium_Copyright_A...

This shit is absolutely dystopian. The law must not just be reversed, manufacturers need to be taken to court for shoddy software. Insecure data collection and transmission should be treated the same as having unsafe electrical wiring. It is a defect that needs to be either fixed or the product recalled. As long as manufacturers are not just allowed to but rewarded for selling defective products this won't change. I expect the moment unsolicited data collection becomes a liability manufacturers will drop it like a hot potato.

Re: Vacuum bricked after user blocks data collection – user mods it to run anyway

#24

[flagged]

> Why would they not be homogenous? Why would a business have the power to decide what should and what shouldn't be homogeneous about the property of others? A transaction took place, property has legally changed hands and the former owner is exerting control over property that isn't theirs any more. How about if the builder of your house comes into your home via an access route unknown to you, and starts rearranging…

> How about if the builder of your house comes into your home via an access route unknown to you, and starts rearranging where things are placed, or where you and your wife are placed, etc. in order to maintain homogeneous layout?

And if you complain he kicks you and your wife out of the house you bought. And if you dare to close off the backdoor he sends you to jail.

Re: Vacuum bricked after user blocks data collection – user mods it to run anyway

#25
Never connected my Roomba to the internet and it has worked fine for the past several years. It insists that I should connect to it via the app to resolve the occasional minor issue, but I would always ignore those. It's starting to show its wear and it's probably time for a new vacuum. I'm not sure if I'll be able to bootstrap one without connectivity, nowadays. Any good recommendations out there?

Re: Vacuum bricked after user blocks data collection – user mods it to run anyway

#26
post #6

I block this nonsense before it gets to the cash register.

That's always a good idea, but how many people have the resources to research these details? First of all you have to be aware that this issue even exists. Then you have to scrape the corners of the internet for whether an appliance has any anti-features, because no manufacturer will ever write "collects unsolicited data about you, we will break the appliance if you refuse us your personal information" on the box. And finally you need to be able to afford the time and patience for the whole process.

I don't own a smart vacuum cleaner because the trouble is not worth it to me. However, I can see smart vacuum cleaners being very good for elderly or disabled people, or someone who has very limited free time and could let the robot clean the house on its own while the owner is out. It is really disgusting that scumbag manufacturers are exploiting those people.

Re: Vacuum bricked after user blocks data collection – user mods it to run anyway

#27

Never connected my Roomba to the internet and it has worked fine for the past several years. It insists that I should connect to it via the app to resolve the occasional minor issue, but I would always ignore those. It's starting to show its wear and it's probably time for a new vacuum. I'm not sure if I'll be able to bootstrap one without connectivity, nowadays. Any good recommendations out there?

You might be interested in this project https://valetudo.cloud/

They have a list of supported vacuums

Re: Vacuum bricked after user blocks data collection – user mods it to run anyway

#28
post #23

"From there, he built a Raspberry Pi joystick to manually drive the vacuum, proving that there was nothing wrong with the hardware." He should make these and sell them. It would be worth it to just drive it in "discovery" mode and give it the exact path to follow while cleaning. The constant inability to learn the floor plan is beyond annoying.

Depending on where he lives this might be illegal. Yes, we live in a cyberpunk dystopia where the manufacturer can break what you bought and then send you to jail for repairing it. You can read more about it here: https://consumerrights.wiki/w/Digital_Millennium_Copyright_A... This shit is absolutely dystopian. The law must not just be reversed, manufacturers need to be taken to court for shoddy software. Insecure da…

>>>>> I expect the moment unsolicited data collection becomes a liability manufacturers will drop it like a hot potato.

Possession of the data needs to be illegal.

Here's how it could work. It's similar to how copyrights for music are enforced. A person whose data are found in someone's files or server can sue for "statutory" damages, which are levied on a per-offense basis.

Re: Vacuum bricked after user blocks data collection – user mods it to run anyway

#29
Probably a felony under the DMCA.

I'm reminded of when AWS us-east-1 went down and all the beds made by EightSleep (business model: Juicero for beds) became disabled. EightSleep put all the significant control for their beds in the cloud, doubtless because they couldn't or didn't know how to hire embedded engineers, and the only devs they could find were node.js flunkies who only knew how to do cloud. Looks like the makers of this vacuum did the same thing; they didn't know how or didn't want to build just enough smarts to do the localization and mapping itself, and said "fuck it, we'll do it in the cloud".

Post reply on HN