Spaceflight Now shared their video of the explosion, which the Orlando Sentinel describes as showing Blue Origin's rocket "become engulfed in flames. The fireball expands out and covers the entire launch pad as the fuselage of the rocket can be seen crumbling into the flames."

Blue Origin founder Jeff Bezos said on X.com "It's too early to know the root cause but we're already working to find it. Very rough day, but we'll rebuild whatever needs rebuilding and get back to flying. It's worth it." (SpaceX founder Elon Musk posted "Sorry to see this, I hope you recover quickly.")

It's unclear how this will impact future launches. "The rocket was destroyed," reports CBS News, "and as the smoke cleared, there was no sign of the erector-gantry used to move the New Glenn from its hangar to the pad and to raise it from horizontal to vertical. Likewise, one of two tall lightning towers was no longer visible." It was the first such on-pad explosion at the Cape since a SpaceX Falcon 9 rocket blew up on nearby pad 40 on Sept. 1, 2016... Blue Origin only has one New Glenn pad, the one that was damaged in the Thursday test. The New Glenn, which has launched three times, is a heavy lift rocket designed to compete head-to-head with SpaceX Falcon 9 and Falcon Heavy rockets. During New Glenn's most recent flight in April, an upper stage malfunction prevented a commercial internet satellite from reaching its planned orbit...

The New Glenn destroyed Thursday was to send 48 Leo internet satellites owned by Amazon into space [which were not on board for the hot-fire test]
Blue Origin posted on X.com that "Debris from our recent hotfire anomaly may wash ashore in the coming days/weeks. If you encounter any debris, do not touch or approach it for your safety."

"Spaceflight is unforgiving, and developing new heavy-lift launch capability is extraordinarily difficult..." NASA Administrator Jared Isaacman posted on X.com. "âWe will provide information on any impacts to the Artemis and Moon Base programs as it becomes available."

Thanks to long-time Slashdot reader symbolset for sharing the news.

Slashdot reader alternative_right writes: Quantum computers need extreme cold to work, but the very systems that keep them cold also create noise that can destroy fragile quantum information. Scientists in Sweden have now flipped that problem on its head by building a tiny quantum refrigerator that actually uses noise to drive cooling instead of fighting it. By carefully steering heat at unimaginably small scales, the device can act as a refrigerator, heat engine, or energy amplifier inside quantum circuits.

"An engineer got curious about how his iLife A11 smart vacuum worked and monitored the network traffic coming from the device," writes Tom's Hardware.

"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... 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... [H]e decided to disassemble the thing to determine what killed it and to see if he could get it working again...

[He discovered] 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.
Thanks to long-time Slashdot reader registrations_suck for sharing the article.