Many people who use water cooling in their computer systems like to go full-bore with ‘aquarium’ aesthetic, which includes adding a window to their cooling blocks so that they see the water flowing through the window from behind the case’s window. Traditionally PMMA acrylic is used for these windows, as it’s quite durable and easy to handle.

Using glass offers some advantages over acrylic, but has its own disadvantages, most of all that it’s hard to process, but also that it’s known for shattering quite easily if pushed beyond its limits.

This is why [der8auer] as a manufacturer of such water blocks has now spent a few years investigating the viability of using glass for this purpose. First and foremost is safety, with an early prototype glass water block suddenly shattering without clear cause.

Although normally the water cooling loop is only expected to experience pressures of about 600 mbar, the new glass windows that are now entering mass-production had to be tested to their breaking point. This involves pumping water into a few test blocks until they fail, using the test rig that you can see above.

First the big GPU water block was tested, with the acrylic version breaking at around 8-9 bar, while the glass plate shattered at around 5 bar. The failure mode was also interesting, with the glass plate shattering into fragments, while the two acrylic plates tested failed in a completely different location and manner.

A smaller water block with glass window failed at about 10 bar, demonstrating mostly that smaller glass windows are a lot sturdier. Effectively glass windows in water cooling loops are viable, and they also do not suffer from e.g. discoloration, but you do give up a big chunk of your safety margin if your water cooling loop suffers a major pressurization event. Which of course should never happen, but we’re definitely looking forward to the upcoming field trials of these new water blocks.

youtube.com/embed/_jIqtapkDRo?…

hackaday.com/2026/02/22/testin…

We’ll start things off this week with some breaking news from NASA: just days after the space agency announced the Artemis II crew was preparing to blast off towards the Moon as soon as March 6th, a new problem with the Space Launch System rocket has pushed the launch back indefinitely. According to NASA Administrator Jared Isaacman, problems encountered while loading helium into the Interim Cryogenic Propulsion Stage (ICPS) necessitate rolling the massive rocket back to the Vehicle Assembly Building (VAB) for diagnosis and repair.

The logistics of shuffling the vehicle 6.8 kilometers (4.2 miles) from the pad to the VAB is going to eat up at least a week, and sending it back the other way is naturally just as much of a production. Add in the time they’ll need to actually figure out what’s wrong with the ICPS and make the necessary repairs, and it’s easy to see why a March launch is almost certainly off the table. It’s frustrating to see the Artemis II mission get delayed this close to launch, but sending humans into space isn’t the sort of thing you can cut corners on.

Boeing’s Uber rating is in shambles.
Well, you’d think so at least. This week NASA also released a scathing report detailing the multitude of technical issues that came up during the 2024 test flight of Boeing’s CST-100 Starliner spacecraft. While astronauts Butch Wilmore and Suni Williams eventually made it back home safely aboard a SpaceX Dragon, the space agency has still categorized it as a Type A mishap — their highest incident classification and the same rating given to the losses of Apollo 1, Challenger, and Columbia.

On the subject of companies we love to hate, a recent post by Brian Merchant on his blog Blood in the Machine (awesome band name, called it) points out the precipitous rise in Flock attacks. That is, folks are taking matters into their own hands and destroying the surveillance devices all over the US. Now Hackaday certainly isn’t condoning the destruction of anyone’s property, but we definitely appreciate the rebellious cyberpunk vibe.

Before you go out hunting for Flocks, keep in mind that at least one person has caught a charge already. In fact Jefferey Sovern picked up thirteen charges, as that’s how many Flock cameras he managed to bag before the law caught up to him. According to reports, he also admitted to “keeping some of the wiring, batteries and solar panels taken from the cameras.” Sounds like Jeff would fit in just fine around these parts.

Looking for some new wheels? Got a handy source of hydrogen? If so, you might be in luck. According to CarBuzz, the resale value of Toyota’s Mirai has absolutely cratered. When they were sitting on the lot a new Mirai would have cost you a bit more than $50,000, but on the second-hand market you can get last year’s model for as little as $15,000. If you’re not too picky, you can get one even cheaper. We did a little searching of our own, and found a 2021 Mirai with less than 40K miles for just $9,000. That’s an insane price for a mid-size luxury car, but of course it doesn’t really matter how cheap the car is if you can’t find anywhere to fill the thing up.

Finally, the folks at F-Droid have sounded the alarm about some concerning changes Google has planned for Android. As we first covered back in October, anyone looking to develop applications for the world’s most popular mobile operating system will soon have to register with Google through a process which is still not entirely clear. Although the search giant has hinted that the system will feature some special consideration for students and hobbyists, F-Droid isn’t convinced. Until there is more transparency, they are urging developers and Android users to push back via keepandroidopen.org.

See something interesting that you think would be a good fit for our weekly Links column? Drop us a line, we’d love to hear about it.

hackaday.com/2026/02/22/hackad…

Meshtastic has been experiencing a bit of a renaissance lately, as the off-grid, long-range radio text messaging protocol gains a ton of new users. It’s been used to create mesh networks in cities, during disasters and protests, in small groups while hiking or camping, and for search and rescue operations. Although it’s connected plenty of people together in all of these ways, [GreatScott!] wanted to put it to work connecting some computing resources instead. He has a garden shed that’s too far for WiFi, so Meshtastic was used to connect it instead.

This isn’t a project to bring broadband Internet out to the shed, though; Meshtastic is much too slow for that. All he really wanted to do here was to implement a basic alarm system that would let him know if someone had broken in. The actual alarm triggering mechanism is an LED emitter-detector pair installed in two bars, one of which sends a 12V signal out if the infrared beam from the other is broken. They’re connected to a Heltec ESP32 LoRa module which is set up to publish messages out on the Meshtastic communications channel. A second module is connected to the WiFi at the house which is communicates with his Home Assistant server.

Integrating Meshtastic devices into Home Assistant can be pretty straightforward thanks to the various integrations already available, but there is some configuration to get these specific modules working as an alarm. One of the pins on the remote module had to be set up to watch the light bar, and although sending the alarm message out when this triggered worked well, the received signal never passed through to Home Assistant until [GreatScott!] switched to using the RadioLib library an an MQTT integration instead. But with perhaps more configuration than he planned for out of the way, [GreatScott!]’s alarm is up and running. Meshtastic projects often balloon into more than we had originally planned though, in more ways than one. You can follow along as our own [Tom Nardi] attempts to connect all of New Jersey with this new protocol.

youtube.com/embed/nC0o99nN2D0?…

hackaday.com/2026/02/22/meshta…

You might not have noticed, but we here at Hackaday are pretty big fans of Open Source — software, hardware, you name it. We’ve also spilled our fair share of electronic ink on things people are doing with AI. So naturally when [Jeff Greerling] declares on his blog (and in a video embedded below) that AI is destroying open source, well, we had to take a look.

[Jeff]’s article highlights a problem he and many others who manage open source projects have noticed: they’re getting flooded with agenetic slop pull requests (PRs). It’s now to the point that GitHub will let you turn off PRs completely, at which point you’ve given up a key piece of the ‘hub’s functionality. That ability to share openly with everyone seemed like a big source of strength for open source projects, but [Jeff] here is joining his voice with others like [Daniel Stenberg] of curl fame, who has dropped bug bounties over a flood of spurious AI-generated PRs.

It’s a problem for maintainers, to be sure, but it’s as much a human problem as an AI one. After all, someone set up that AI agent and pointed at your PRs. While changing the incentive structure– like removing bug bounties– might discourage such actions, [Jeff] has no bounties and the same problem. Ultimately it may be necessary for open source projects to become a little less open, only allowing invited collaborators to submit PRs, which is also now an option on GitHub.

Combine invitation-only access with a strong policy against agenetic AI and LLM code, and you can still run a quality project. The cost of such actions is that the random user with no connection to the project can no longer find and squash bugs. As unlikely as that sounds, it happens! Rather, it did. If the random user is just going to throw their AI agent at the problem, it’s not doing anybody any good.

First they came for our RAM, now they’re here for our repos. If it wasn’t for getting distracted by the cute cat pictures we might just start to think vibe coding could kill open source. Extra bugs was bad enough, but now we can’t even trust the PRs to help us squash them!

youtube.com/embed/bZJ7A1QoUEI?…

hackaday.com/2026/02/22/what-a…

Mega Man is a popular video game character who is perhaps most notable for having a sort of lasery-type blaster for an arm. A real hand cannon, if you will. It’s officially called the Mega Buster, and [Arnov Sharma] recently recreated it for cosplay purposes.

Key to any good cosplay build is getting the visuals right, and [Arnov] achieved that well. The Mega Buster was first recreated in Fusion 360, scaled to an appropriate size to fit [Arnov]’s arm. It was 3D printed in several sections, with the body including a grab handle and fire button inside, and the side panel and blaster nozzle having provision for installing LEDs. The former is the blaster’s “power meter” which shows how many shots it has left until it runs out of energy, with the blaster able to fire six times before needing to cooldown. A Raspberry Pi Pico controls the LEDs and provides sound effects with the aid of a PAM8403 class D amplifier module and a small speaker.

The 3D files are available on Instructables for the curious. Perhaps by virtue of its arm-mounted nature, this build reminds us of the venerable Pip Boy from Fallout, of which we’ve seen many grand recreations before. Video after the break.

youtube.com/embed/CMXTvWcF8Cg?…

hackaday.com/2026/02/22/recrea…

Recently [ElecrArc240] got his paws on an Intel-branded 3 kW power supply that apparently had been designed as a reference PSU for servers. At 3 kW in such a compact package air cooling would be rather challenging, so it has a big water block sandwiched between the two beefy PCBs. In the full teardown and analysis video of the PSU we can see the many design decisions made to optimize efficiency and minimize losses to hit its 80 Plus Platinum rating.

For the power input you’d obviously need to provide it with 240 VAC at sufficient amps, which get converted into 12 VDC at a maximum of 250 A. This also highlights why 48 VDC is becoming more common in server applications, as the same amount of power would take only 62.5 A at that higher voltage.

The reverse-engineered schematic shows it using an interleaved totem-pole PFC design with 600 V-rated TI LMG3422 600V GaN FETs in the power stages. After the PFC section we find a phase-shifted full bridge rectifier with OnSemi’s SiC UF3C065030K4S Power N-Channel JFETs.

There were a few oddities in the design, such as the Kelvin source of the SiC JFET being tied into the source, which renders that feature useless. Sadly the performance of the PSU was not characterized before it was torn apart which might have provided some clues here.

Schematic diagram of the AC-DC circuit in the 3 kW, 12VDC power supply. (Credit: ElectrArc240, YouTube)
youtube.com/embed/da9GwXX-0Zs?…

hackaday.com/2026/02/22/inside…

As far as punctuation goes, the exclamation mark is perhaps the most eye-catching of the bunch. That’s why [Conrad Farnsworth] thought this form would be perfect for his Home Assistant notifier build.

The key to this build is the large bi-color printed housing in the shape of an exclamation mark. It makes for an attractive wall-hanging, but it also perfectly serves the purpose [Conrad] had in mind. Inside the enclosure is an ESP32, hooked up to a string of 16×8 LED matrixes which are commanded over I2C. These sit behind a white panel in the enclosure to nicely diffuse the light and make their output more readable. The ESP32 displays notifications on the LEDs that are fed from Home Assistant, such as when the mailbox sensor is triggered or if a vehicle is detected in the driveway. There’s also a bell on the unit to provide audible notifications, which us dinged with a solenoid fired via a 2N2222 transistor switching a 12-volt supply from a boost converter.

It’s a neat build that fits nicely into [Conrad]’s daily life and appears to have some genuine utility. If you’re looking for other ways to neatly display notifications where you can see them, you might consider whipping yourself up a smart mirror. Video after the break.

youtube.com/embed/C5UuRmCwZ78?…

hackaday.com/2026/02/22/exclam…