Personal note: I got sick and very depressed. Was only out of bed for 4 to 6 hours only. So much bad happened in a short period of time that I couldn’t deal. I plan to do a video someday on it. But everything from being on the gurney with iv’s in my hand only to learn they couldn’t do my cataract surgery to the car engine seizing and then the van needing 2 grand in repairs. That was enough but Ron did not measure the placement of the bathroom project water lines, so things did not fit. It all had to be redone and so we changed where things were going. But just as I started to feel better and had more energy I went to fix a problem on my computers. I reset the video one thinking I had the extended updates for a year. But resetting it wiped that out. So for the last few days I have learned about Linux systems and tried to install them. The first one Ubuntu installed but I couldn’t get the line commands to work. The second installed and worked but faulted out. Every attempt to install one since has failed. I am wiping and then reactivating the hard drive to see if that will work. If not I will have to add a new processing chip and or motherboard to the list of things I can’t afford but need. That is why I have not been around much. Best wishes to all and hugs to those that want them.

Smart Robot Vacs Don’t Look As Attractive To Me,

unless someone’s able to override an override of an override. I’m not familiar with this publication; this was another story I read during a jog, but the story seems feasible. Experts here will know. I’m just tossing it in here.

Manufacturer issues remote kill command to disable smart vacuum after engineer blocks it from collecting data — user revives it with custom hardware and Python scripts to run offline

News By Jowi Morales published 15 hours ago

The smart vacuum cleaner was remotely bricked for not collecting data.

An engineer got curious about how his iLife A11 smart vacuum worked and monitored the network traffic coming from the device. That’s when he noticed it was constantly sending logs and telemetry data to the manufacturer — something he hadn’t consented to. The user, Harishankar, decided to block the telemetry servers’ IP addresses on his network, while keeping the firmware and OTA servers open. While his smart gadget worked for a while, it just refused to turn on soon after. After a lengthy investigation, he discovered that a remote kill command had been issued to his device.

He sent it to the service center multiple times, wherein the technicians would turn it on and see nothing wrong with the vacuum. When they returned it to him, it would work for a few days and then fail to boot again. After several rounds of back-and-forth, the service center probably got tired and just stopped accepting it, saying it was out of warranty. Because of this, he decided to disassemble the thing to determine what killed it and to see if he could get it working again.

Since the A11 was a smart device, it had an AllWinner A33 SoC with a TinaLinux operating system, plus a GD32F103 microcontroller to manage its plethora of sensors, including Lidar, gyroscopes, and encoders. He created PCB connectors and wrote Python scripts to control them with a computer, presumably to test each piece individually and identify what went wrong. From there, he built a Raspberry Pi joystick to manually drive the vacuum, proving that there was nothing wrong with the hardware.

From this, he looked at its software and operating system, and that’s where he discovered the dark truth: his smart vacuum was a security nightmare and a black hole for his personal data. First of all, it’s Android Debug Bridge, which gives him full root access to the vacuum, wasn’t protected by any kind of password or encryption. The manufacturer added a makeshift security protocol by omitting a crucial file, which caused it to disconnect soon after booting, but Harishankar easily bypassed it. He then discovered that it used Google Cartographer to build a live 3D map of his home.

This isn’t unusual, by far. After all, it’s a smart vacuum, and it needs that data to navigate around his home. However, the concerning thing is that it was sending off all this data to the manufacturer’s server. It makes sense for the device to send this data to the manufacturer, as its onboard SoC is nowhere near powerful enough to process all that data. However, it seems that iLife did not clear this with its customers. Furthermore, the engineer made one disturbing discovery — deep in the logs of his non-functioning smart vacuum, he found a command with a timestamp that matched exactly the time the gadget stopped working. This was clearly a kill command, and after he reversed it and rebooted the appliance, it roared back to life.

So, why did the A11 work at the service center but refuse to run in his home? The technicians would reset the firmware on the smart vacuum, thus removing the kill code, and then connect it to an open network, making it run normally. But once it connected again to the network that had its telemetry servers blocked, it was bricked remotely because it couldn’t communicate with the manufacturer’s servers. Since he blocked the appliance’s data collection capabilities, its maker decided to just kill it altogether. “Someone—or something—had remotely issued a kill command,” says Harishankar. “Whether it was intentional punishment or automated enforcement of ‘compliance,’ the result was the same: a consumer device had turned on its owner.”

Unfortunately, many other smart vacuum brands use similar hardware, so it’s not far-fetched to think that they have the same setup. This is likely especially true for cheaper devices that have less capable hardware and aren’t capable of edge computing, meaning they’ll have to send the data to some faraway server for processing. But because your information is being offboarded to another device outside of your control, you really have no idea what’s happening to it, giving the manufacturer free rein to use it as it pleases.

In the end, the owner was able to run his vacuum fully locally without manufacturer control after all the tweaks he made. This helped him retake control of his data and make use of his $300 software-bricked smart device on his own terms. As for the rest of us who don’t have the technical knowledge and time to follow his accomplishments, his advice is to “Never use your primary WiFi network for IoT devices” and to “Treat them as strangers in your home.” (snip)

Got A Hatch Sunrise Alarm Clock?

I didn’t even know these clocks existed until I read about them on the phone during a jog. All in all, this seems like a very first world problem complete with hysterics, considering all that is going on around us, but these clocks might frighten a person of faith. (So do they understand what faith literally means?)

Christian Influencers Are Throwing Their Hatch Clocks in the Trash

The popular sunrise alarm clock company stirs up controversy with its horror-themed Halloween ads and programming.

Few sunrise alarm clocks have reached the level of popularity set by Hatch, the combination light and sound machine designed to help support natural circadian rhythms. Which is why I was surprised to notice it trending on TikTok, not for its gentle sunrise light feature or recently released Hatch+ programming—but for being a symbol of the occult.

The problem began, innocently enough, with an anti blue light promotional campaign, released by Hatch on October 13 and titled “Goodnight, Phone.” It consists of a one-minute, 30-second Hollywood-esque trailer starring actress Kiernan Shipka, who delivers a convincing scream-queen performance with the theme that blue light exposure after your bedtime can lead to nightmarish sleep. The trailer is, admittedly, a bit PG-13—Shipka pulls a long, bloody phone cord out of her mouth, and is attacked by a zombie version of herself in bed.

“It’s Time to Sleep”

With a Hatch device and a subscription to Hatch+, users are able to change their alarm sounds, from white noise and ocean waves to the “hoa hoa hoa” introduction from the vampire classic Twilight, and Hatch+ is also promoting its library of Halloween-themed bedtime stories, like a narration of “The Legend of Sleepy Hollow.”

For some, the creepy trailer and vampire-themed Hatch+ programming were a bridge too far, and by October 24, according to Hatch, the brand found itself trending on “DemonTok,” the TikTok hashtag for discussions of monsters, demons, and related subjects.

As “Hatch demonic ad” and “Is the Hatch alarm clock demonic?” quickly became top search terms, several users posted videos of themselves throwing their devices into the trash in protest, including TikTok Christian influencer Charity, who goes by the username “CharityIsMe.” (snip-there is MORE)

A Flag, Sons Who Housekeep, & More, In Some Items I Read Yesterday

The items don’t have to do with each other; they interested me or looked like something I ought to know about, so I read them and thought someone else might like to read one or another or maybe all of them.

=======================

What the Fascist Tech Bros Get Wrong About Prometheus

=============

Caught in Partition’s Violent Fray

Snippet:

The 1947 partition of the South Asian subcontinent into India and Pakistan led to the world’s largest mass migration. Populations from both sides of newly formed demarcations suffered in heinous riots. Women in particular were subjected to extreme violence. Yet, the severity of gendered crime during Partition wasn’t caused by an arbitrary upsurge of madness. Systemic patriarchy in South Asia had long reduced women to male-owned property. They were objectified to such an extent that a woman’s sexual “purity” became a metonym of her husband’s and kinsmen’s honor (izzat). In other words, male respectability was gauged by how successfully women’s bodies were regulated. With Partition, this dynamic became a forum for contesting powers and prestige at the communal and national levels.

To assert manhood and symbolize triumphal power over the enemy, rivaling sides opted for sexually charged violence, grotesquely marking, mutilating, and branding the bodies of women. According to historian

“[T]housands of women on both sides of the newly formed borders,” writes historian Urvashi Butalia,

were abducted, raped, forced to convert, forced into marriage, forced back into what the two states defined as “their proper homes,” torn apart from their families once during Partition by those who abducted them, and again, after Partition, by the state which tried to “recover” and “rehabilitate” them.

In the guise of celebrating independence from British rule, official narratives of nationalism largely omitted female experiences of such violence during the divisive convulsions of 1947. Among the earliest Partition texts that documented gory details which would have otherwise slithered into oblivion is Pinjar (which can translate to both “Skeleton” and “Cage”), a novella by Amrita Pritam that captures the cataclysmic years of Partition via a series of abductions.

*Amrita Pritam, New Delhi, 1979. via Wikimedia Commons*

A writer celebrated for both powerful poetry and prose, Amrita Pritam (1919–2005) is a well-known figure in South Asian literature. Inspired by real life, much of her work serves as testimony. Pritam witnessed firsthand the horrors of Partition—communal riots forced her to migrate to India from Pakistan in 1947 with nothing but her two small children and a red shawl. She never returned home. (snip-MORE on their page linked above)

==========================

Designing Intersex History: Behind the Intersex Flag with Morgan Carpenter

The Intersex Human Rights Fund (IHRF) at the Astraea Lesbian Foundation for Justice is celebrating its 10th year of funding intersex liberation efforts across the globe. Join us in reflecting on the IHRF’s many accomplishments, intersex movement successes, and our vision for the future of intersex organizing.

Created in 2013 by Morgan Carpenter, an intersex man based in Australia, the intersex flag was intentionally designed to stand out, communicate values important to intersex communities, and be used widely and freely. The intersex flag has a simple design: a bold purple circle on a bright yellow background. The circle represents many things, including wholeness and bodily autonomy, while the colors yellow and purple both represent the strength and diversity of intersex communities while avoiding all references to gender.

(Snip-a bit MORE)

====================

Vacuuming, laundry, and doing the dishes: My life as a ‘trad son’

Plenty of us are living back at home, adopting ‘traditional’ duties in exchange for free accommodation – Charlie Aslet

When I read the term “trad sons” on my phone, I spat the hot cocoa my mother had prepared for me out onto the screen. “What fresh torture will the live-at-home generation be subjected to next?” I cried. It only got worse when I scrolled to see that mothers were calling their stay-at-home sons “hubsons”, a play on the word husbands. “Has the whole world gone Oedipal?” I exclaimed in horror.

Following on from the trend of the “tradwife”, the internet has coined the term trad sons for children who stay at home with their parents and adopt “traditional” sonly duties in exchange for free accommodation. (Snip-MORE, it’s not long)