Your Browser Probably Lies To The Big Sites (Blame Chrome)

May 16, 2026 by 2 Comments

When you visit certain large sites in Firefox or Safari, the browser may detect your visit and change its behavior. It could be as simple as lying about its identity, or it may totally change how it renders the page. But according to a post by [Den Odel], this isn’t a conspiracy between browsers and big Internet — rather, it is a byproduct of Chrome’s dominance.

Here’s how it goes. Chrome puts out a new feature and everyone rushes to implement it on their site. Maybe the new code breaks other browsers. Maybe the other browser supports the feature, but the website doesn’t detect it correctly or is unaware. Maybe it just relies on some quirk of Chrome. Regardless, Firefox and Safari will change to match the site rather than mess up the user’s experience.

If you want to check it out, Firefox will show you what it does and let you disable specific fixes if you visit the about:compat URL. For Safari, you’ll have to read code from a file named quirks. Bugzilla tracks the fixes for Firefox, if you want more details.

Browsers are huge and complex so even niche browsers, today, usually use one of a handful of rendering engines. It seems that the question isn’t if a big company should control the way the web works. It is more a question of which one is currently dominating.

Asimov Is An Open Source Humanoid Robot For The Rest Of Us

May 16, 2026 by 4 Comments

Given that some of the more famous demos were by Honda and Tesla, you might be forgiven for thinking you need pockets as deep as a car company to get into humanoid robotics — and maybe that was true once, but now Asimov v1 is here. It doesn’t have a positronic brain, and you’ll have to code in the Three Laws for yourself, but at least you have the freedom to, because Asimov is open source. 

It’s not exactly cheap: the kit version comes with a target price of $15,000 USD, but they do provide the Bill of Materials on the GitHub repository so you can try and hunt down some deals. Still, compared to the millions poured into these sorts of robots in the early days, we have to consider it accessible. With 25 total degrees of freedom, you’ll have to source a lot of actuators, but at least the onboard compute will be easy to get. Rather than begging CERN for spare positrons, you’ only need a Raspberry 5 and a Radaxa CM5.

No word on if this robot can write a symphony — though we’ve seen software that can — and its 5 kg personal best for squats and 18 kg single-arm lat raises aren’t going to impress the bros at the gym. But hey, at least now you have someone to shake your chair for sim gaming.  If you’re wondering what the deal with these androids is, well, so were we.

After Stumbling From CVE To CVE Will Linux Get A Kill Switch?

May 16, 2026 by 11 Comments

For the few people who have spent the past weeks living under a security rock, the Linux kernel has found itself the subject of multiple severe bugs in the form of Copy Fail and Dirty Frag, both of which allow for privilege escalation. They’ve made many people very upset, and also potentially put many thousands of systems at risk of exploitation. Worse is that system managers are generally left to twiddle their thumbs while waiting for patches to be rolled out. This is where NVIDIA engineer [Sasha Levin] has proposed a ‘kill switch’ for affected kernel functions.

The basic concept seems rather simple, with this feature merely intercepting a call to the affected function and instead returning a predefined return value. This makes it less extreme than hitting a general SCRAM button on the entire kernel, and could theoretically allow the affected systems to keep running until the patched kernel becomes available.

A disadvantage of this is that it obviously modifies the kernel, patching it in-memory so that you need to reboot the system to clear it. Another potential disadvantage is that it opens a potentially massive attack vector, with people in the Cybersecurity sub-Reddit roundly rejecting the idea. Amidst all the other anxious conversions there is also the concern that this particular patch was at least partially generated by an LLM (Claude Opus 4.7) , so one may hope that if it does gets merged into mainline it’ll at least be properly vetted by multiple pairs of well-caffeinated human eyes.

What a punch card looks like to openCV

21st Century Punch Cards Are 3D Printed And Read By OpenCV

May 16, 2026 by 8 Comments

While a punch card is perhaps the lowest-density storage medium available, it has some distinct advantages. As [Bitroller] points out in the write-up of his punch card project, if he was using stainless steel instead of PLA his 3D printed punch cards would likely outlast everything he owns, and survive a five-alarm fire to boot. If you have 16 bytes you really, really don’t want to forget — or are willing to store your private key in a shoe box — this project might be of interest.

The nice part is that he’s built a handy Python script to generate printable files for the punch cards, which encode 16 bytes of information and 4 bytes of error correction using the Reed-Solomon algorithm. That’s just enough for a password and the error correction means up to two bytes can be recovered in the case of read failure.

The reading is where this gets interesting — again, [Bitroller] provides a handy script, but this one uses OpenCV to read the entire punch card at once from a webcam image, using the contrast between a black table and the light-colored PLA cards. It’s massively overkill and would have needed a supercomputer in the days when punch cards were common I/O, but that’s what makes this a great hack.

We only have one quibble: if you use additive manufacturing, can you still call it a punch card? Nothing was punched out, after all.

If you think punch cards are totally irrelevant in the modern day, well, you might be right– but that doesn’t stop us from playing with them. If punch cards make you think of Big Iron in the early days of computing, maybe think further back– they were used for everything from Jacquard looms to the original MIDI.

Salvaged VFDs In Nixie-Like Clock

May 16, 2026 by 3 Comments

In between the Nixie tube era of the 50s and 60s and the advent of multi-digit vacuum fluorescent displays (VFDs) common in 80s and 90s consumer technology, there was a brief time in the early 70s where single-digit VFDs were commonplace. Superficially these devices look like Nixie tubes, but have a number of advantages to them including lower voltage, lower power requirements, and lower cost. [maurycyz] recently found a number of these salvaged from old calculators and used them to build a retro-themed clock.

[maurycyz] was not able to find datasheets for this display, but was able to reverse-engineer each of the digits. Similar to vacuum tubes there is a heater which has a few ohms of resistance, and from there each of the segments of the digit can be deduced by probing the 13 signal wires. These are analog devices in some respects, so a lot of experimentation had to go into driving the displays to find their optimal conditions. A quartz crystal was used for timekeeping with an AVR128DA28 microcontroller chosen to provide control for the digits, using seven pins as segment drivers and four as grid drivers. Each digit uses around 0.14 watts, so with all four digits on it can consume a little over half a watt. A simple wood enclosure rounds out the build.

As Nixie supply wears thin, VFDs like this can be an excellent stopgap or replacement while still building retro-themed displays like this clock or this calculator which uses similar VFDs for each digit.

Fixing A Cotton Candy Vending Machine

May 16, 2026 by 3 Comments

Cotton candy is probably the best way to eat pure sugar, which makes having your very own cotton candy vending machine to automate making it a bit of a dream. The machine that [Block’s Retro Repairs] got should therefore make him very happy, but unfortunately it was bought as defective. After digging into the machine in an earlier video, this time around there’s some actual success and proper cotton candy to enjoy.

The PCB with the rather frayed temperature sensor. (Credit: Block's Retro Repairs, YouTube)
The PCB with the rather frayed temperature sensor. (Credit: Block’s Retro Repairs, YouTube)

The way that cotton candy is made involves spinning thin threads of sugar, which are created by the heating and rapid crystallization of the sweet stuff. Unfortunately this machine wasn’t even really extruding sugar any more, so it had to get a deep clean to remove probably years of crusty buildup. After this things still weren’t working right, although cranking up the temperature on the induction heated head improved the results somewhat.

To really fix the machine, this head with its clearly dodgy thermocouple had to be disassembled. This revealed that said sensor was looking rather frayed, potentially shorting out against the aluminium head and likely not in the entirely right position any more. After adding some insulation back and making sure that the thermocouple was located closer to the top of the head, it was time for more testing.

Repairing the thermocouple seems to have fixed most ills, with still some calibration of the temperature required, but finally resulting in fancy shaped cotton candy in its myriad of colors. Along with the looming hazard of potentially acquiring Type II diabetes from all the testing, there was still a problem involving the remote management feature of this Red Rabbit machine.

These $6,000 vending machines do feature an Android 7-based software with a Rockchip SoC and access to a lot of settings via its large touch screen, but features such as setting prices for the products are locked away via a remote account. The machine was sadly still linked to someone else’s account, and so far Red Rabbit support had not responded to any documentation, repair help or account unlinking requests. This has left the machine in somewhat of a pickle.

It was possible to dump the software of the machine, which can be fetched from Archive.org, so if anyone would like to pitch in and break this remote lock, that would be very welcome. It’s also considered to replace the cash reader with a simple button or so, but where’s the fun in that?

Continue reading “Fixing A Cotton Candy Vending Machine” →

Mixapps: The Mixtape Of The Internet Age

May 16, 2026 by 35 Comments

Mixtapes used to be a way that we cultivated a personal selection of music for our own enjoyment, or to give as gifts to those we wanted to impress with a personal touch. These days, we’d typically try that with a playlist, but it’s less romantic despite also being more ephemeral. Songs fall off streaming services all the time, and few of us have the exact same subscriptions as those we’re trying to flirt with. Thus, [Hunter Irving] whipped up a more lasting solution for this modern age.

The concept is simple—it’s a collection of songs that are packaged together in a easily portable format that won’t disappear because of corporate bureaucratic nonsense. [Hunter] has termed their project Mixapps—because it’s a method of sharing music based around Progressive Web Apps (PWA). To create a custom mix, you start by running a Python script, which will then let you add tracks and reorder them as you desire. From there, you run a second script that builds the web app for you.

You can then upload the prepared app directory to a web host to share it with anyone you like. They can then save the PWA to the home screen of their mobile device, where it will live happily ever after. There’s no need to keep hosting the app online or for the user to remain connected to the Internet; everything is self contained on their device. If you’re curious, there’s a demo you can check out online.

It’s worth noting that there are intellectual property concerns to be had as with any form of music sharing, but what else is new? We’ve explored the magic of mixtapes in the past, anyway, to be sure. If you’re finding new ways to trade music and playlists, romantically or platonically, don’t hesitate to let us know.