The Agony Of Packaging Linux Apps

One of the great things of Linux as an ecosystem is that there is so much choice. Yet this is also its greatest weakness, as unlike on MacOS and Windows this means that simple questions often do not have a simple answer. The topic of distributing software is one of these vexing topics that never really goes away, with [Noam Lewis], as author of the Fresh editor, recently expressing their frustrations on this topic.

This is a familiar topic that we have covered before, mostly in the context of cross-platform installers. Whereas on MacOS and Windows you just pick any of a handful of standard installer frameworks that do roughly the same thing, on Linux you are dealing with a dizzying number of package managers, including distro-specific ones, NPM, Homebrew, Rust crates, third party repositories like Arch Linux’s AUR or stray APT repositories for Debian, and of course AppImage and Flatpak along with a host of other options.

After going through the entire list with help from the Fresh community, [Noam] ended up creating packages for all of them, and has a lot of thoughts. Since Fresh is a TUI-based editor, something like Flatpack is not a really good fit, while AppImage is just very slow due to mounting the image, which is annoying.

Overall, distro-specific solutions are just unpleasant in general, as they mean repeating the same work over and over, even if you can even get into a distribution channel. Ultimately the solution that [Noam] ended up at was to have a static binary with the musl runtime, along with an integrated updater, which is a solution that should be quite familiar for Windows users. Yet even if it fails some kind of purity test for certain Linux users, is it really a bad solution if it works for users of the software?

Read A USB Logitech Racing Wheel On An ESP32‑S3

Now that MCUs like the ESP32-S3 are quite capable computer systems including USB host functionality, it only makes sense that you can connect USB peripherals like Logitech racing wheels to them. Of course, these aren’t basic HID USB devices, so they require a bit of setup to make them start spitting out the data updates which we’re interested in. Making this process easy is the goal of the LogiWheelHost project for ESP32-S3 by [Joel Kometz].

This single-header library supports the G29, G923, G920, G27, G25, DFGT, Driving Force Pro wheels, building on top of the EspUsbHost project. As explained in the README, these racing wheels do not start streaming all updates to their controls once powered on, but boot into a restricted mode in which only neutral or combined-axis data is sent.

To change this you need to trigger the so-called native mode switch in which far more detailed information as well as updates on extended features like separate pedals, all buttons and the gear shifter become available. This is done by sending a HID output report to the USB device, which is easy enough.

In addition to handling this detail the library also provides an API using which obtaining and using these controller states in your own code should be quite easy. Presumably the library will work on or can be ported to other ESP32 MCUs that support host USB mode, so this might be good news for anyone who is looking to do more with that old Logitech racing wheel.

Procrastineers Rejoice! 2026 Supercon Call For Participation Extended

A few weeks ago, we put out the call for participation for this year’s 2026 Hackaday Supercon, taking place in Pasadena, CA this November. Today was going to be the deadline, but like you, we often let things pile up and put things off, so we’re extending another two weeks until August 26th.

Which is not to say that we haven’t heard from a ton of you! We’re psyched to see so many familiar Supercon regulars on the list, but we also love to see first-timers give talks. We try to make sure that new folks get their time to shine, so if you’ve never given a Supercon talk before, or if it’s been a few years, take this as your cue to present in front of the friendliest audience of like-minded hackers around.

This year is Hackaday’s tenth in-person Superconference, and to celebrate we’ve gotten a larger venue, so more folks can watch the talks live. We’ll be running two tracks as always, and you have your choice of a 20-minute or 40-minute slot. Presenters get in free, and we’ll get you an early-bird ticket rate the submission, so don’t delay and register for your slot today! Or at least before August 26th, because we won’t extend the deadline twice.

Oh, and if you’re interested in tickets, swing by Hackaday about this time tomorrow — we’ll have some news for you.

Watch Today’s Eclipse At Home

In a few hours, there is a solar eclipse that will be visible with a track that goes from Spain up through Greenland. Too late to travel for it, but thanks to [jonty], you can find all the webcams that will have a view.

This may be ideal. No funny glasses. No looking at a projected image on a card. Of course, many, if not all, of these cameras aren’t looking directly at the sun, so it isn’t clear if you’ll be able to see the actual eclipse or just the effect it has on the surroundings.

Continue reading “Watch Today’s Eclipse At Home”

Getting Back Into Resin Printing: First Results

When we last left off, I had just set up a new SLA resin printer and was on the verge of doing the initial round of printing to see just how resin printing in 2026 compares to way back in 2020. Surely SLA printing had to be easier and less fussy than it was in 2020?

During these weeks of printing, setting up printers and taking a gander at the various workflows that certain printers and their manufacturers try to push you into I have both produced a series of not too shabby prints and some delightful spaghetti. I also flipped a few proverbial tables and formed some strong opinions on 3D printing workflows, of which some can considered to be family-friendly.

Without further ado, let’s get into some updates, a bit of ranting, and even some printing results.

Continue reading “Getting Back Into Resin Printing: First Results”

3 KB Solitaire Fits In QR-Code, Runs In DOS

In these days of hundred-gigabyte-and-more monster games, it can be nice to stop and remember what a human can do with assembly language and very, very little storage space. In this case, only 3 KB — yes, three kilobytes — to play TinySol, a tiny solitaire game for DOS that’s compatible with the common CGA/EGA/VGA graphics modes. [ClassicBits] even fits the 640×400 AT&T 6300 mode that was used for some GRiD computers in that 3 KB.

The “full” version is actually 3.5 KB. That extra half kilobyte gets you the ability to load and save games, plus mouse support. The 3 KB version you must play through to the end using only the keyboard, but if you’re hitting this on the minimal-supported-hardware target of the IBM 5150, you probably don’t have a mouse. The smaller build can still score the game, auto-finish, congratulate you on a win, and even automatically detect the correct graphics mode for you. It can also be launched from a QR code, which [LGR] demonstrates in a video embedded below. Check it out for a play demo, but it’s Klondike Solitaire. If you don’t know what to expect by this point, you must not have used a PC in the last 30 years.

Even smaller versions of TinySol are available if you know you’re only going to need, say CGA, but even with 360 KB floppies we’re not sure we’d feel the need to save a kilobyte. If it doesn’t fit on the floppy, just print it onto the sleeve as a QR code, like [ClassicBits] did with the floppies he was giving away at Vintage Computer Festival Southwest 2026. Well, technically that’s the “Tiny” version on the QR code, but we have faith there’s some visual code that could hold the 3 KB “medium” game.

[ClassicBits] takes care to point out that his game is 100% human-written, which is something you cannot guarantee even for retro assembly-language products. We’ve already seen that Claude can code for the Z80, which means the 8088 won’t escape it either. Of course these old machines have a lot to recommend them if you want to escape modernity and learn to code without the help.

Continue reading “3 KB Solitaire Fits In QR-Code, Runs In DOS”

Lighting 3D Printed Parts On Fire For Science

Although lighting 3D prints on fire is rarely the intended outcome, it’s possible that said print will at some point in its future come into contact with either an open flame or a significant source of heat. Once that happens, what will be the result and how worried should one be? This is basically the excuse behind [Maker’s Muse] recent decision to light some 3D prints on fire.

Crispy 3D printed combat robot. (Credit: NHRL)
Crispy 3D printed combat robot. (Credit: NHRL)

Materials exposed to an open flame in this experiment included various types of PLA, PETG, ABS, ASA, TPU and PEBA. Since PLA filaments have a significant amount of carbon in them it’s little wonder that these burned quite readily, though an interesting difference was immediately visible between an Elegoo PLA+ test cone and a Prusa Galaxy Black PLA cone. The latter required a blow torch to properly ignite, after which it burned rather hot whilst melting, unlike the dirty yellow flame of the PLA+.

So-called ‘high temperature’ PLA (HTPLA) seems to actively resist burning, self-extinguishing after a blowtorch treatment. Just these few samples of PLA already gave very different results, with very likely the additives being the defining factor since pure PLA is easy to burn as a way to dispose of it somewhat cleanly.

Moving on, black PETG didn’t really want to ignite, while ABS and ASA absolutely love to burn with a sooty yellow flame. HIPS was also tested, burning in a similar sooty manner as well.

Of all the materials tested, TPU was the least flammable with even the blowtorch not able to start ignition and only melting the sample. Foam TPU did however burn the most aggressive, followed by ABS, ASA and HIPS. Overall PETG and regular TPU seem to be your best bet if you do not want your 3D print to turn into a happily burning candle and potentially a general fire hazard.

Continue reading “Lighting 3D Printed Parts On Fire For Science”