Illustrated Kristina with an IBM Model M keyboard floating between her hands.

Keebin’ With Kristina: The One With The Grasshopper Typewriter

Do you consider your keyboard to be a fragile thing? Meet the glass keyboard by [BranchNo9329], which even has a glass PCB. At least, I think the whole thing is glass.

The back side of an all-glass keyboard. Yeah.
Image via [BranchNo9329] via reddit
There are so frustratingly few details that this might as well have been a centerfold, but I thought you all should see it just the same. What we do have are several pictures and a couple of really short videos, so dive in.

I can tell you that [BranchNo2939] chose a glass substrate mainly due to curiosity about its durability compared with FR4. And that the copper circuitry was applied with physical vapor deposition (PVD) technology.

Apparently one of [BranchNo2939]’s friends is researching the bonding of copper on to glass panels, so they thought they’d give a keyboard a go. Right now the thing is incomplete — apparently there’s going to be RGB. Because of course there’s going to be RGB. Continue reading “Keebin’ With Kristina: The One With The Grasshopper Typewriter”

Hackaday Links Column Banner

Hackaday Links: March 23, 2025

What a long, strange trip it’s been for NASA astronauts Suni Williams and Bruce Wilmore, who finally completed their eight-day jaunt to space after 289 days. The duo returned to Earth from the ISS on Tuesday along with two other returning astronauts in a picture-perfect splashdown, complete with a dolphin-welcoming committee. For the benefit of those living under rocks these past nine months, Williams and Wilmore slipped the surly bonds way back in June on the first crewed test flight of the Boeing Starliner, bound for a short stay on the ISS before a planned return in the same spacecraft. Alas, all did not go to plan as their ride developed some mechanical difficulties on the way upstairs, and so rather than risk their lives on a return in a questionable capsule, NASA had them cool their heels for a couple of months while Starliner headed home without them.

There’s been a lot of talk about how Butch and Suni were “stranded,” but that doesn’t seem fair to us. Sure, their stay on the ISS was unplanned, or at least it wasn’t Plan A; we’re sure this is always a contingency NASA allows for when planning missions. Also unfortunate is the fact that they didn’t get paid overtime for the stay, not that you’d expect they would. But on the other hand, if you’re going to get stuck on a work trip, it might as well be at the world’s most exclusive and expensive resort.

Continue reading “Hackaday Links: March 23, 2025”

Thanks For Hackaday Europe!

We just got back from Hackaday Europe last weekend, and we’re still coming down off the high. It was great to be surrounded by so many crazy, bright, and crazy-bright folks all sharing what they are pouring their creative energy into. The talks were great, and the discussions and impromptu collaborations have added dramatically to our stack of to-do projects. (Thanks?) Badges were hacked, stories were shared, and a good time was had by all.

At the event, we were approached by someone who wanted to know if we could replicate something like Hackaday Europe in a different location, one where there just isn’t as vibrant a hacking scene. And the answer, of course, was maybe, but probably not.

It’s not that we don’t try to put on a good show, bring along fun schwag, and schedule up a nice location. But it’s the crowd of people who attend who make a Hackaday event a Hackaday event. Without you all, it just wouldn’t work.

So in that spirit, thanks to everyone who attended, and who brought along their passions and projects! It was great to see you all, and we’ll do it again soon.

Hackaday Podcast Episode 313: Capacitor Plague, Wireless Power, And Tiny Everything

We’re firmly in Europe this week on the Hackaday podcast, as Elliot Williams and Jenny List are freshly returned from Berlin and Hackaday Europe. A few days of mingling with the Hackaday community, going through mild panic over badges and SAOs, and enjoying the unique atmosphere of that city.

After discussing the weekend’s festivities we dive right into the hacks, touching on the coolest of thermal cameras, wildly inefficient but very entertaining wireless power transfer, and a restrospective on the capacitor plague from the early 2000s. Was it industrial espionage gone wrong, or something else? We also take a moment to consider spring PCB cnnectors, as used by both one of the Hackaday Europe SAOs, and a rather neat PCB resistance decade box, before looking at a tryly astounding PCB blinky that sets a new miniaturisation standard.

In our quick roundup the standouts are a 1970s British kit synthesiser and an emulated 6502 system written in shell script, and in the can’t-miss section we look at a new contender fro the smallest microcontroller, and the posibility that a century of waste coal ash may conceal a fortune in rare earth elements.

Follow the link below, to listen along!

Want the podcast in MP3?  Get it in MP3!

Continue reading “Hackaday Podcast Episode 313: Capacitor Plague, Wireless Power, And Tiny Everything”

This Week In Security: The Github Supply Chain Attack, Ransomware Decryption, And Paragon

Last Friday Github saw a supply chain attack hidden in a popular Github Action. To understand this, we have to quickly cover Continuous Integration (CI) and Github Actions. CI essentially means automatic builds of a project. Time to make a release? CI run. A commit was pushed? CI run. For some projects, even pull requests trigger a CI run. It’s particularly handy when the project has a test suite that can be run inside the CI process.

Doing automated builds may sound straightforward, but the process includes checking out code, installing build dependencies, doing a build, determining if the build succeeded, and then uploading the results somewhere useful. Sometimes this even includes making commits to the repo itself, to increment a version number for instance. For each step there are different approaches and interesting quirks for every project. Github handles this by maintaining a marketplace of “actions”, many of which are community maintained. Those are reusable code snippets that handle many CI processes with just a few options.

One other element to understand is “secrets”. If a project release process ends with uploading to an AWS store, the process needs an access key. Github stores those secrets securely, and makes them available in Github Actions. Between the ability to make changes to the project itself, and the potential for leaking secrets, it suddenly becomes clear why it’s very important not to let untrusted code run inside the context of a Github Action.

And this brings us to what happened last Friday. One of those community maintained actions, tj-actions/changed-files, was modified to pull an obfuscated Python script and run it. That code dumps the memory of the Github runner process, looks for anything there tagged with isSecret, and writes those values out to the log. The log, that coincidentally, is world readable for public repositories, so printing secrets to the log exposes them for anyone that knows where to look.

Researchers at StepSecurity have been covering this, and have a simple search string to use: org:changeme tj-actions/changed-files Action. That just looks for any mention of the compromised action. It’s unclear whether the compromised action was embedded in any other popular actions. The recommendation is to search recent Github Action logs for any mention of changed-files, and start rotating secrets if present. Continue reading “This Week In Security: The Github Supply Chain Attack, Ransomware Decryption, And Paragon”

Linux Fu: A Warp Speed Prompt

If you spend a lot of time at the command line, you probably have either a very basic prompt or a complex, information-dense prompt. If you are in the former camp, or you just want to improve your shell prompt, have a look at Starship. It works on the most common shells on most operating systems, so you can use it everywhere you go, within reason. It has the advantage of being fast and you can also customize it all that you want.

What Does It Look Like?

It is hard to explain exactly what the Starship prompt looks like. First, you can customize it almost infinitely, so there’s that. Second, it adapts depending on where you are. So, for example, in a git-controlled directory, you get info about the git status unless you’ve turned that off. If you are in an ssh session, you’ll see different info than if you are logged in locally.

However, here’s a little animation from their site that will give you an idea of what you might expect: Continue reading “Linux Fu: A Warp Speed Prompt”