These days there are emulators for all the great consoles of yesteryear, as well as old retrocomputers and arcade machines and so much else to boot. Now, though, a particularly popular MP3 player has an emulator of its own—by the name of clicky!

The name is a reference to the click wheel of the venerable Apple iPod, and as you might imagine, that’s precisely what clicky is built to emulate. [daniel5151] started the project as a neat technical challenge, following on from earlier work he’s done in the NES emulation space. The iPod is a bit of a difficult prospect to emulate, being very much a closed-source device that is very poorly documented in the public space. There are few projects to look to for help, since a complete open-source iPod emulator doesn’t already exist; however, various alternative firmware projects have offered a guiding light.

For now, clicky can boot into RetailOS, which is what you would have used on an iPod you bought from the factory. It can also run Rockbox and iPodLinux, though for now, running the Apple Diagnostics program is not yet achievable. Plenty of functionality still isn’t implemented, either, like USB communication or even audio, which was the iPod’s whole raison d’être. Still, you can play some Brick Breaker like it’s 2006 if you’ve been missing it badly.

We see all kinds of emulators around these parts; this 60 FPS NES emulator running on a microcontroller was a particularly impressive recent effort. If you’re cooking up your own emulators for unique platforms, or unique emulators for non-unique platforms, let us know on the tipsline!

hackaday.com/2026/08/26/emulat…

This week Jonathan chats with Nathan Freitas of the Guardian Project! What is going on at the forefront of Open Source and privacy advocacy? Where are we on a true Tor browser on iOS? And what’s the ideal solution to the Android Lockdown issue? Watch to find out!

• cyber.harvard.edu/people/nfrei…
• guardianproject.info/feed/
• proofmode.org/feed/

youtube.com/embed/9YZSyin4r_4?…

Did you know you can watch the live recording of the show right on our YouTube Channel? Have someone you’d like us to interview? Let us know, or have the guest contact us! Take a look at the schedule here.

play.libsyn.com/embed/episode/…

Direct Download in DRM-free MP3.

If you’d rather read along, here’s the transcript for this week’s episode.

Places to follow the FLOSS Weekly Podcast:

• Spotify
• RSS

Theme music: “Newer Wave” Kevin MacLeod (incompetech.com)

Licensed under Creative Commons: By Attribution 4.0 License

hackaday.com/2026/08/26/floss-…

Quite a few in our community make a bit of cash on the side by selling our creations, and it’s not uncommon to find that a project which catches your eye can be picked up as a kit for a few of your preferred currency units. But there’s a problem facing such tiny producers in the form of regulations intended for large businesses which are beyond their ability to comply with. [Alain Pannetrat] writes for the Lectronz marketplace about one of them, the new European Union packaging waste regulations.

At face value it sounds like a good idea, that suppliers should be responsible in some way for the disposal of their packaging. It discourages excessive packaging and encourages recycling, indeed the EU even describe the scheme as boosting business. The problem is that its administration is left to individual member states, and someone selling across the whole bloc would have to join multiple schemes. The hefty price is nothing to a large enterprise, but impossible for a tiny one. He makes a very good point, that it’s difficult to claim to champion innovation, while also imposing something like this on grass-roots innovators. Going by the experiences of our acquaintances in this space an extra burden on top of that presented by the current unstable tariff and customs situation involved in selling to the USA would likely be the straw which broke the camel’s back.

In practice we suspect that many are simply doing the same as they have with compliance marking and waste electronic equipment regulations, simply not bothering and hoping they fly under the radar and never get caught. We hope we won’t end up reporting on any future crackdown, the landscape has definitely changed since we tried our hand in this business.

hackaday.com/2026/08/26/how-pa…

Printed circuit boards were developed first for function over form. They were a way to mount components and connect them in a stable, robust fashion, while taking into regard things like packaging and cooling requirements to enable a circuit to function. Circuit boards often end up looking cool in a techy kind of way, but their aesthetic is usually very much secondary to their actual purpose.

Katrin Dietzsch likes to use her PCBs a little differently, however. She designs boards that are intended to be a narrative tool for tabletop roleplaying, and came down to Hackaday Europe 2026 to walk us through the development of this very whimsical hardware.

Roll For It

youtube.com/embed/hO1hAOewLhw?…

Katrin starts her talk by explaining how she came to design circuits specifically for tabletop gaming. She saw an opportunity to combine her hardware hobby with the world of TTRPGs to help maintain both hobbies amidst a busy lifestyle. She also found that hardware she built could be a great artistic medium for supporting mystery and storytelling in the tabletop world. With the right design, her circuits became very much part of the narrative themselves.
Getting to see Katrin’s PCB D20 is a highlight of the talk. It’s a great example of creative board design.
How does one create a piece that becomes special, rather than just being another art project thrown in a drawer, though? Katrin notes that meaningful objects are the ones that gather stories about them and gain emotional baggage, and thus, relevance. Interaction is also key; she relates the familiar tale that many of us have yelled at a printer before. We often anthropomorphize objects or assign them personalities just because they have some level of strange behaviour, or even if they just blink at us. Often, she’ll also start a build not from specs, but from story and the game itself. The questions asked are about how to engage players, and how to help them reach their goals, and answering those can help guide the design process.

There are also elements drawn from typical ideas around magic and artifacts that can be drawn from. For example, many tabletop roleplaying games feature the concept of attunement, where a character may have to physically and spiritually connect with an object to access its magical features. This is something that can be readily recreated in the electronic world with the use of things like capactive touch sensing. Katrin also notes that using RF can be great for creating items or puzzles that respond based on proximity, and there is all sorts of fun to be had with things like IR beams, motors, switches, or whatever else players can interact with. Code is also a beautiful place to hide secrets and easter eggs—you get to write the behaviour of the device to be as beguiling and confounding as you like.
You could use paper maps… or perhaps you could whip up a PCB with traces and solder mask and silkscreen and interactivity all woven together to create something altogether more compelling and interactive. There are grand possibilities in this space for your tabletop game to transcend the usual.
There’s also the visual side of things. It’s something that should be remarkably familiar to anyone who has been to a modern hacker or maker convention and seen the wonderful variety of badge designs created by the community. Everything from the copper layers to the silkscreen to the very routing of the fiberglass board itself can be leveraged to create an art piece that captivates and inspires. Particularly in this era when it’s so easy to find board houses that will produce your designs with soldermask in all the colors of the rainbow. Katrin’s wonderful D20 PCB serves as the perfect example of these techniques being applied well.

Like any good tabletop aficionado, Katrin has a great sense of practicality too. There’s no point designing some fantastic electronic gizmo for your game if you can’t afford the bill of materials, can’t solder the parts, or your players can’t figure out how they’re supposed to use an in-circuit programmer to interact with it. Most of us live very busy lives, so our hobby projects have to be achievable within the constraints of our lifestyle. She also notes that it’s great if you build something with longevity, rather than something that serves only as a single-use tchotchke for a one-off bit.

If you’ve ever contemplated bringing your electronics skills to bear in your role as a dungeon master, Katrin’s talk is a great place to start. Your little creations can serve as a wonderful bridge between your player’s experience and the world of imagination you’re collectively creating, and that’s always a fun time!

hackaday.com/2026/08/26/hackad…

Large language models (LLMs) are generally thought of as machines that accept textual prompts and spit out textual content. However, if you’re creative in the way you interface with them, you can get them to do a wider range of tasks. For example, [Andrea Ricci] figured out how to get one to play DOOM.

For this project, [Andrea] began by porting the game to the SCINTIX P4. It’s a rather interesting device, being a single board designed in the Raspberry Pi CM4/CM5 form factor, but carrying an ESP32-P4 and an ESP32-C6 instead. The game runs on the P4 and is displayed on a 1024×600 MIPI DSI panel, but it’s only stepped through a few frames at a time. These frames are then passed to Claude Sonnet via a WebSockets setup. With only the same information as a human player would get, the LLM has to figure out what it’s looking at, and then respond with movement and fire commands to play the game.

It’s quite interesting to watch the system play—the LLM mostly accurately describes the game world, navigates down corridors, opens doors, and shoots at enemies. There is a bit of work behind the scenes to enable it to see and understand the game world—namely, using a depth fan across the field of view so it can figure out where walls are and how not to bang into them. There’s also an ASCII automap used to allow the system to keep track of where it has already been. But fundamentally, the LLM is playing the game without any other sort of additional assistance.

We’ve seen some other great ways in which AIs have been whipped up to play various games, like Trackmania.

youtube.com/embed/z6UT_tOvC2Q?…

hackaday.com/2026/08/26/claude…

The vulnerability landscape shifted significantly in Q2 2026. First, the number of registered CVEs reached an unprecedented level. This is driven primarily by the widespread adoption of AI, both for application development and search for security flaws. This resulted in entire new classes of vulnerabilities emerging, particularly in the Linux networking subsystem.

Second, security researchers have been publishing exploits for unpatched vulnerabilities more frequently. Publications like these can generate significant fallout, since they potentially open the door for attackers to target unprotected systems.

Statistics on registered vulnerabilities

This section provides statistical data on registered vulnerabilities. The data comes from Kaspersky’s vulnerability knowledge base, which draws on the CVE database as well as the Russian BDU database and GitHub Advisory (GHSA). As a result, the figures for previous reporting periods may differ from those published in earlier reports.

We examine the number of registered vulnerabilities for each month over the last five years. As the chart below shows, this number continues to surge, a trend reflected across all the databases we track. It’s driven primarily by the widespread adoption of AI tools: as we predicted in our previous report, these tools have played a major role in the discovery of vulnerabilities in third-party software. Meanwhile, these tools often contain security issues of their own. For example, OpenClaw, a popular AI project, ranked 12th among those with the highest number of vulnerabilities discovered and published in Q2, with over 200 CVEs registered during the reporting period. Finally, AI development tools are also contributing to the vulnerability landscape, since the quality of the code they produce can vary widely. Therefore, the rate at which new vulnerabilities are discovered will inevitably keep growing.

Total published vulnerabilities per month from 2022 through 2026 (download)

Next, we analyze the number of new critical vulnerabilities (CVSS > 9.0) over the same period.

Total critical vulnerabilities published per month from 2022 through 2026 (download)

As the chart shows, the number of published critical vulnerabilities jumped sharply in Q2. This is because using AI for vulnerability research makes it possible to analyze massive amounts of previously unexamined code, uncover new attack surfaces, and identify entire classes of vulnerabilities that have gone unnoticed for decades. In particular, AI was used to find a series of Dirty Frag vulnerabilities in the Linux kernel.

Exploitation statistics

This section presents statistics on vulnerability exploitation for Q2 2026. The data draws on open sources and our telemetry.

Windows and Linux vulnerability exploitation

Q2 2026 saw a new precedent in the publication of vulnerabilities in Windows components and exploits for these: researchers no longer waiting for CVE registration, let alone patches. A case in point: a researcher who goes by Nightmare Eclipse (also known as Chaotic Eclipse) published a list of new “named” vulnerabilities across various Windows subsystems. At the time the technical details were published, none of the vulnerabilities had been assigned a CVE identifier:

• BlueHammer: a local privilege escalation vulnerability in Windows Defender. During signature database updates, a time-of-check to time-of-use (TOCTOU) race condition occurs, allowing an attacker to substitute the directory where temporary update files are written. The researcher published a fully functional exploit for the vulnerability.
• RedSun: another logical vulnerability in Windows Defender with a working exploit. Suspicious and malicious files marked as “cloud” can be overwritten or restored to their original directory with elevated privileges. The exploit incorporates fragments of algorithms that make it possible to leverage various logical vulnerabilities in Windows, effectively combining a large number of popular exploitation techniques.
• YellowKey: a vulnerability that lets the user bypass BitLocker full-disk encryption and access system data through the Windows Recovery Environment (WinRE). A fully functional exploit was also published.
• GreenPlasma: a vulnerability that enables system object injection via the CTF loader for the Collaborative Translation Framework (CTFMON) service in Windows. The original publication included an exploit with limited functionality.
• RougePlanet: yet another Windows Defender vulnerability that, like BlueHammer, stems from a TOCTOU issue, this time in the engine responsible for real-time system scanning. The published exploit uses the vulnerability to overwrite the system file wermgr.exe with a malicious one.
• UnDefend: another vulnerability in the Windows Defender service. This time, the exploit causes a denial of service and blocks updates.

Even though such cases remain isolated for now, we believe they’ll grow into a full-fledged trend. Early publication of exploits gives attackers an advantage over software developers, who are left with no time to fix the issues.

Veteran vulnerabilities in Windows software also remain relevant. These are the ones our solutions most frequently detect exploits for:

• CVE-2018-0802: a remote code execution (RCE) vulnerability in the Equation Editor component
• CVE-2017-11882: another RCE vulnerability also affecting Equation Editor
• CVE-2017-0199: a vulnerability in Microsoft Office and WordPad that allows an attacker to gain control over the system
• CVE-2023-38831: a vulnerability in WinRAR that involves improper handling of objects within an archive
• CVE-2025-6218 (formerly ZDI-CAN-27198): another WinRAR vulnerability allowing the specification of relative paths to extract files into arbitrary directories, potentially leading to malicious command execution
• CVE-2025-8088: a vulnerability similar in exploitation method to CVE-2025-6218. The attackers used NTFS Streams to circumvent controls on the directory into which files are being unpacked

The vulnerabilities listed here can be leveraged to gain initial access to a vulnerable system and for privilege escalation. This underscores the critical importance of timely software updates.

That said, the number of Windows users who encountered exploits declined slightly in Q2, hitting an 18-month low.

Dynamics of the number of Windows users encountering exploits, Q1 2025 – Q2 2026. The number of users who encountered exploits in Q1 2025 is taken as 100% (download)

Linux also hit a rough patch in Q2 2026. Specifically, the period saw the disclosure of the Dirty Frag family of vulnerabilities, which lets an attacker reliably escalate privileges within the operating system.

All the vulnerabilities published in Q2 2026 were, in one way or another, related to the Linux caching subsystem. Here are the ones being most actively exploited:

• CVE-2026-31431 (Copy Fail): a local privilege escalation vulnerability in the Linux kernel that lets an unprivileged user modify the page cache and gain root privileges. Especially dangerous for cloud and containerized environments
• CVE-2026-43284, CVE-2026-43500 (Dirty Frag): a family of vulnerabilities in the Linux networking subsystem (IPsec ESP and RxRPC) that lets a local user overwrite the page cache and escalate privileges to root
• CVE-2026-46300 (Fragnesia): a local privilege escalation vulnerability in the Linux kernel related to packet fragment handling and the page cache mechanism. It lets an unprivileged user gain root privileges and is also classified as part of the Dirty Frag family
• CVE-2026-31635 (DirtyDecrypt): a Linux kernel vulnerability that lets a local attacker escalate privileges due to improper handling of decryption operations and page cache data modification
• CVE-2026-43494 (PinTheft): a Linux kernel vulnerability that lets a local user gain elevated privileges due to errors in the memory page pinning mechanism
• CVE-2026-46331 (pedit COW): a vulnerability in the Linux kernel’s traffic control subsystem (tc-pedit) that exploits a flaw in copy-on-write to modify the page cache and subsequently escalate privileges to root

The vulnerabilities described above were quickly embraced by attackers. At the same time, our solutions continue to detect exploitation attempts targeting older vulnerabilities as well:

• CVE-2022-0847: a vulnerability known as Dirty Pipe, which enables privilege escalation and the hijacking of running applications
• CVE-2019-13272: a vulnerability caused by improper handling of privilege inheritance, which can be exploited to achieve privilege escalation
• CVE-2021-22555: a heap out-of-bounds write vulnerability in the Netfilter kernel subsystem
• CVE-2023-32233: another Netfilter subsystem vulnerability that allows for Use-After-Free conditions and privilege escalation through improper processing of network requests

Dynamics of the number of Linux users encountering exploits, Q1 2025 – Q2 2026. The number of users who encountered exploits in Q1 2025 is taken as 100% (download)

In Q2 2026, the number of Linux users who encountered exploits declined slightly compared to Q1. Given that a significant share of new vulnerabilities are tied to the operating system’s caching subsystem, we recommend installing patches as quickly as possible, or disabling vulnerable kernel modules if patching isn’t an option.

Most common published exploits

The distribution of published exploits by software type in Q2 2026 includes categories that haven’t appeared in the sample for a long time. For instance, we’re once again seeing exploits targeting SharePoint. It’s worth noting that while several vulnerability write-ups for Exchange and SharePoint were published during the quarter, most turned out to be fake, AI-generated research. While the articles and exploit source code themselves look fairly polished, they describe nonexistent problems in the software or its components — often close to genuinely vulnerable mechanisms — in order to mislead researchers. This type of attack is aimed at increasing the time it takes to detect real vulnerabilities. In some cases, the description of a nonexistent vulnerability came bundled with completely unrelated malware.

Distribution of published exploits by platform, Q1 2026 (download)

Distribution of published exploits by platform, Q2 2026 (download)

Vulnerability exploitation in APT attacks

We analyzed which vulnerabilities were exploited in APT attacks during Q2 2026. The rankings provided below include data based on our telemetry, research, and open sources.

TOP 10 vulnerabilities exploited in APT attacks, Q2 2026 (download)

In Q2 2026, a trend emerged in APT attacks toward exploiting new vulnerabilities right from the moment they’re published. As before, we’re also seeing a large number of zero-day vulnerabilities. The Langflow vulnerability deserves particular attention: it’s one of the first cases of an APT group exploiting AI technology, which many organizations are only just beginning to integrate. Because most of this tech is proprietary, it has a considerable number of security blind spots. Therefore, given the growing number of AI-based automation tools, we strongly recommend going beyond the usual patching and developing secure procedures for credential use and sensitive data handling in systems that rely on agents and LLMs.

C2 frameworks

In this section, we examine the most popular C2 frameworks used by APT groups and analyze the vulnerabilities targeted by the exploits that interacted with C2 agents in APT attacks.

The chart below shows the frequency of known C2 framework usage in attacks during Q2 2026, according to open sources.

TOP 10 C2 frameworks used by APTs to compromise user systems, Q2 2026 (download)

Sliver, Havoc, AdaptixC2, and Metasploit remain the most widely used C2 frameworks. After studying open sources and analyzing samples of malicious C2 agents that contained exploits, we determined that the following vulnerabilities were utilized in APT attacks involving the C2 frameworks mentioned above:

• CVE-2026-35273: a vulnerability in Oracle PeopleSoft PeopleTools that security vendors classify as server-side request forgery (SSRF). The details of the vulnerability have never been disclosed, although some research covers the post-exploitation steps
• CVE-2023-46604: an insecure deserialization vulnerability in Apache ActiveMQ that allows arbitrary code execution in the context of the service process
• CVE-2024-12356 and CVE-2026-1731: command injection vulnerabilities in BeyondTrust software that allow an attacker to send malicious commands even without system authentication
• CVE-2023-36884: a vulnerability in the Windows Search component that allows commands to be run on the system, bypassing the mark-of-the-web (MoTW) mechanism
• CVE-2025-53770: an insecure deserialization vulnerability in Microsoft SharePoint that allows for unauthenticated command execution on the server
• CVE-2025-8088 and CVE-2025-6218: similar directory traversal vulnerabilities in WinRAR that allow files to be extracted from an archive to a predetermined path, potentially without the archiving utility displaying any alerts to the user

These vulnerabilities show that attackers used them for initial access and privilege escalation on vulnerable systems, setting the stage for launching a C2 agent. They include both zero-day vulnerabilities and fairly well-known security issues.

LLM/AI tool vulnerabilities

This section analyzes data published in Kaspersky’s vulnerability knowledge base. We reviewed the Q2 2026 version of the knowledge base.

As mentioned above, AI tools, plugins, and technologies have proven fairly effective at automating the search for problematic code and anomalous behavior. The high speed at which new vulnerabilities are being discovered has naturally created a need to fix them just as quickly. AI is often used for this too, which increases the volume of code being generated. However, neither code written without human involvement nor AI-generated advice is always correct.

The chart below covers registered vulnerabilities in AI tools for 2025–2026.

Number of published vulnerabilities in LLMs, AI tools, and plugins with similar functionality, 2025–2026 (download)

As the charts show, AI tools are racking up a substantial number of registered vulnerabilities, and that number keeps growing quarter over quarter. It’s also worth looking at how AI tool vulnerabilities break down by type, according to the CWE system:

TOP 6 vulnerability types in products that implement or use AI/LLM logic, 2025–2026

Interestingly, vulnerabilities of an undetermined type have ranked first in every quarter since the start of 2025. Traditionally-made software has the same issue, and it doesn’t look like the growing number of AI tools will fix it. It’s also notable that the list includes classes CWE developers themselves don’t recommend using for vulnerability classification, since they lump together a whole range of more specific types. CWE-284 is an example of this.

Looking at the most common classes, the key issues found in AI-related software can be summed up as follows:

• Inadequate access control over critical system objects
• Improper implementation of authentication and authorization mechanisms
• Injections

It’s worth noting that injection-related vulnerabilities were relatively rare before AI agents took off (previously, they mostly affected web apps). Recently, though, these security issues have become relevant again.

Looking back at a year and a half of the AI boom, one conclusion stands out regarding registered vulnerabilities: AI tool developers are more focused on expanding functionality than on security. This is worth keeping in mind when using these tools. Let’s look at the projects and applications that either integrated AI tools or offered them as the core product. Below is a list of the those with the highest number of registered vulnerabilities for 2025–2026.

TOP AI/LLM-related projects by number of published vulnerabilities, 2025–2026 (download)

Notable vulnerabilities

This section highlights the most significant vulnerabilities published in Q2 2026 that have publicly available descriptions. Since the above already covers several significant vulnerabilities published during the reporting period, this section consists mainly of LLM/AI tool vulnerabilities.

CVE-2026-25253: a gatewayUrl vulnerability in OpenClaw

The issue stems from the fact that the OpenClaw user interface trusts the value of the gatewayUrl parameter passed in the URL and automatically establishes a WebSocket connection to the specified address. During this connection process, it sends an authentication token without any additional user confirmation.

The attack algorithm exploiting this vulnerability works as follows:

1. The application obtains a critical connection address from an external source (the gatewayUrl URL parameter), which is controlled by the attacker.
2. There is no validation before use.
3. The client automatically initiates a connection to the address specified in the parameter, which belongs to the attacker.
4. While connected, the application sends credentials (an access token) to the specified address.

If the attacker obtains a valid token, the consequences depend on that token’s level of access within the system. In general, this could lead to:

• User session compromise
• Execution of operations on the user’s behalf
• Modification of the AI agent configuration
• Unauthorized access to tools and resources connected to the agent
• Under certain OpenClaw configurations, further compromise of the host running the agent

It’s worth noting that the risk of exploitation arises from a combination of several factors: the automatic connection and token transmission, the lack of address trust verification, and the high privileges granted to the local AI agent.

CVE-2026-41948: a path traversal vulnerability in the Dify AI platform

The vulnerability lets an authenticated user craft a request that enables the application to escape its permitted tenant and gain access to internal REST APIs that weren’t meant for that user. The root cause is insufficient normalization and validation of the URL path before it’s passed to the internal service.

Depending on the Dify configuration, the consequences can include:

• Unauthorized access to internal service interfaces
• Breach of isolation between workspaces
• Exposure of internal service information
• Conditions favorable to further attacks when combined with other vulnerabilities

The use of Dify in enterprise AI platforms is particularly risky, since internal services there tend to hold elevated privileges.

CVE-2026-45386: an improper access control vulnerability in Open WebUI

In Open WebUI, pin/unpin operations on messages are write operations, since they modify that message’s metadata (is_pinned, pinned_by, pinned_at). In vulnerable versions, however, before performing these actions, the API only checked for read access to the channel (a chat between a user or group and the AI) containing the message, not permission to modify its content. As a result, a user with a role limited to viewing messages could still change a message’s pinned status.

The vulnerability’s mechanism works as follows:

1. The user initiates an action that changes the state of an object.
2. The application treats this action as a regular read request.
3. Only channel view permission is checked.
4. The application performs a write without verifying the required user authorization.

This violates one of the fundamental principles of access control models — namely, that any operation that changes the state of data must be checked for the appropriate write or moderation permissions, regardless of whether the object itself is readable.

Although the vulnerability doesn’t lead to arbitrary code execution or compromise of sensitive data, it can affect data integrity and collaborative workflows. Potential consequences of exploitation include unauthorized pinning or unpinning of messages, disruption of channel moderators’ and administrators’ activities, changes to the display order of important information, and even the potential spread of false or misleading information by altering the channel containing a pinned message.

Open WebUI is widely used as an interface for interacting with local and enterprise LLMs. In these systems, pinned messages often contain important instructions, announcements, or tips for users. The ability to modify them with minimal privileges can disrupt collaborative workflows, cause confusion, and undermine trust in information published by administrators and moderators.

CVE-2026-45501: a vulnerability in Microsoft Exchange

The vulnerability stems from improper neutralization of user input when generating Exchange web pages. As a result, the browser may interpret specially crafted data as active content instead of plain text.

Although Microsoft categorizes the potential impact of exploiting this vulnerability as spoofing, flaws like this can lead to alteration of displayed content, imitation of trusted interfaces, actions on behalf of the user within an active session, and abuse of user trust.

It’s worth noting that issues like this are still relevant in modern software, given that mechanisms like Content Security Policy and various parsers were specifically created to help developers neutralize dangerous parts of user page content.

Conclusion and advice

Q2 brought the first significant results of AI automation adoption in software development and vulnerability hunting tools. This research shows that beyond traditional patch management, organizations now need real-time monitoring of systems and access controls, since infrastructure and everyday applications now contain far more AI functionality that could lead to compromise.

Accordingly, besides quickly detecting infrastructure vulnerabilities and managing security patches, modern enterprise-grade security solutions need to provide a broad range of preventive measures for tracking the overall health of systems and workstations. Kaspersky Next meets these requirements by combining proactive mechanisms with the ability to respond promptly to emerging threats.

securelist.com/vulnerabilities…

As children, many of us looked wistfully into the cockpits of heavy machinery, wondering just how the series of knobs and levers would do something like operate a bulldozer, crane, or excavator. The nature of these myriad of hydraulic and electronic controls for equipment like this is often inscrutable to adults as well; it takes a considerable amount of training to be able to competently operate most of these machines. But this new controller from MIT may help shorten that training time.

The controller is specifically meant for excavators. In a standard excavator, a pair of joysticks is typically used, with one controlling the swing and the boom and the other controlling the stick and the bucket. Getting used to this combination can take practice, so instead the group of researchers replaced them with a model excavator arm that the operator controls directly with their own arm. The new controller is more intuitive to use as it translates the movements of the model to that of either a real excavator or a training simulation.

The researchers plan to include haptic feedback in future versions, which will hopefully further increase the ease of which new operators can get a feel for using these machines. For those not working towards a new career or an ambitious weekend with rental equipment, there are some other ways of learning how to operate excavators and other pieces of heavy machinery.

hackaday.com/2026/08/26/new-co…

A pyrotechnic charge is set off by passing a high voltage through a filament within it, melting the filament and igniting the charge. We could think of a variety of circuits that could do this, but perhaps we wouldn’t have come up with [Michał Słomkowski]’s solution. He’s used the ringer crank generator from an old military field telephone. It’s an old project he’s shared with us due to its recent republishing on his website.

The basic principle is simple enough, winding the generator charges a capacitor bank through a bridge rectifier. Then a thyristor is used as the trigger device, dumping the contents of the capacitor into the filament. But the full circuit has a couple of refinements. There’s a charge indicator circuit using a couple of Zener diodes and an LED, and a filament tester which passes a non-triggering current through the filament from a 9 volt battery. We like the use of an over-the-top high-current thyristor, no doubt what he had in his junk box.

Perhaps it’s a symbol of how far technology has moved, that today it’s surprisingly rare to find a bridge rectifier or a thyristor, and building this device today would involve a microcontroller and probably an AliExpress inverter module as a matter of course.

Meanwhile, should field telephones interest you, we’ve been there before.

hackaday.com/2026/08/25/blow-t…

[Matt Lenhard] has an interesting writeup explaining exactly how fraudsters offer access to cutting-edge AI models at a tenth of the price. Perhaps unsurprisingly, the secret is to get tokens for free from anywhere they can and by any means necessary. Then wrap them in a pretty relay API, and sell access to it.

Relaying tokens is not by itself a shady practice. That distinction belongs to services that obtain tokens fraudulently, opening the door to selling them at rates far below market value. This practice is widespread and profitable, in part because the abuse is so hard to pin down and stop.

One source of tokens is free credits on new accounts. New accounts are spooled up as fast as possible, hammered until they’re empty, then it’s done all over again. Another method is to sign up as pay-after, possibly with a stolen card, and simply ensure the account has no valid payment method once the bill comes due. Or set up a temporary card, pay some minimum up front and consume as much as possible, then initiate a chargeback. It doesn’t matter if individually each of these doesn’t amount to much before they get flagged, because it’s being leveraged relentlessly on a massive scale by automated systems.

There are the shadier methods, too. Fraudsters don’t just target providers directly. Consumer software products with AI features get reverse-engineered, then the back ends hammered for all they are worth. Poorly-coded support chatbots can be highjacked into serving fraudsters’ traffic instead of just their own. It doesn’t actually matter where the tokens come from, after all. As long as the fraudsters are obtaining them for free (or at least below their costs) then it’s profit.

That last point is one [Matt] zeroes in on with advice on how to mitigate this abuse. He goes into detail in his writeup but what it comes down to is recognizing that it’s a numbers game. Fraudsters depend entirely on obtaining tokens for free, or nearly free. So just like using an AI to keep phone scammers tied up, anything that raises friction increases the fraudster’s costs, in turn encouraging them to find an easier target.

hackaday.com/2026/08/25/cheap-…

Fluid simulations are one of the “killer apps” of high-performance computing, but if you can’t afford the performance, they can take a depressingly long time to run. Depending on your use case, as long as you keep the Reynold’s number in mind– or are just looking for a qualitative look at pretty flows–you might be able to get away with purely-practical simulations using rheoscopic fluid, as [Visual Thinker] demonstrates in a recent video.

The fluid, as you can guess from the name, lets you scope out rheos— that’s flow, for those of you didn’t take Greek. Making it is as simple as you could ask for: get some mica flakes, which are readily available to add ‘sparkle’ to cosmetics, and mix with water and a drop of soap. The soap isn’t always necessary, but depending on your mica it helps keep it in suspension and avoid clumping– [Visual Thinker] found it helped him a good deal. Being flat plates of reflective material, the mica flakes catch the light and sparkle beautifully– and since they align with the fluid shear, they show you exactly what’s going on in your ‘simulation’.

[Visual Thinker] isn’t starting with serious simulations; the first thing he tries is essentially a toy that lets him see fluid flow around a Benchy by sticking magnets in it and using it to move a cross-section of its hull though a thin layer of fluid sandwitched betwixt pieces of laser-cut acrylic. We don’t call it a toy to disparage it, though– we totally want one. [Visual] mentions the idea of a coffee table combining the concept with the kind of underslung mechanism we see in sand drawing tables, which sounds dangerously hypnotic. If any of you build one, please try and tear your eyes away long enough to let us know.

He has another beautiful piece that make the video worth watching: a wind-tunnel, again made of laser-cut acrylic and printed parts. With careful consideration of the scale and flow speeds, that one might actually prove useful– and even if it doesn’t, it’s pretty enough that it doesn’t really matter. Beauty has its own utility sometimes.

Most wind tunnels we see around here use actual wind, but rheoscopic fluid was invented for this sort of thing, even if it does make for pretty baubles.

youtube.com/embed/--Y7vgYxV6g?…

hackaday.com/2026/08/25/reject…

As software updates cease for operating systems, they eventually begin to lose access to parts of the LAN and internet due to out of date encryption features, as well as the inability to handle file sharing protocols like SBM3, which is somewhat of a necessity if you have e.g. a NAS on the LAN. Such too was the case with [watermark_hd]’s 20-year old PowerPC Macs and their installations of OS X Tiger and Leopard.

Cue Aqualink, a native SMB3 client for these older OS X versions that uses [Ronnie Sahlberg]’s libsmb2 server/client library for SMB2 and SBM3. The source code can be found over on GitHub, along with a Japanese translation. By using a local WebDAV server Tiger’s built-in mount_webdav feature can be used to mount these remote volumes.

While you can often still use SMB1 even on modern Windows and Linux/BSD via Samba, allowing even retro systems like these PowerMacs to speak SMB3 is at least a great boost for network security, even if the aforementioned encryption shortcomings mean that you cannot quite run encrypted file shares yet.

Although OS X eventually began to adopt modern SMB versions, some of us may remember how incredibly buggy they were, to the point that us OS X users often had to fall back to CIFS (SMB 1.0), so this is another potential use for this Aqualink application.

hackaday.com/2026/08/25/native…

One of the stories of the last few weeks has been that AI companies have been scanning books in very large numbers in order to train their models with content guaranteed to have been written before 2002, and thus AI free. It’s caused some outrage, because of the size of the operation, and because the scanning process is destructive. In particular the phrase being bandied around is that these are rare books, and it’s this phraseology I find problematic. I think it’s time to unpack why that is the case.

It’s Not Book Burning, Folks

Before I worked for Hackaday I had a long career in and around the publishing industry, mostly on the electronic side, but from time to time crossing paths with my colleagues in the world of paper-based publishing. I understand the appeal of a good book, I’ve spend a lot of my life among bibliophiles, and let’s just say I own a few books myself. In particular I understand the symbolism of destroying books, bringing to mind as it does the actions of repressive regimes. I have stood in Bebelplatz in Berlin where the photo of Nazi student organisation members burning the library of Magnus Hirschfeld’s institute was taken in 1933, and if you know me, you’ll have an idea why that’s close to home. But for all that, what the AI companies are doing is not the same thing.

In this case they’re destroying the books for two reasons. Firstly, as I remember from a previous employer in the publishing world, it’s much easier to digitise a stack of papers than it is a bound book. Thus I’m pretty sure that’s one reason they remove the binding before digitising the pages. Then secondly, as I understand it it’s a copyright issue. If they buy a book, digitise it, and destroy the physical copy, they can legitimately claim that only one copy of it exists, and they hope, sidestep copyright claims from publishers.

When Rare Maybe Isn’t Really Rare At All

You’ll only see one of these numbers on a book published since 1970.
Perhaps the most pertinent question then is just what are the books being scanned and destroyed? They’re almost universally described as “rare”, but is that accurate or sensationalist? It brings to mind a dusty library filled with priceless tomes hand-transcribed by monks which it would be a crime to destroy, but there’s something that explodes that vision in an instant.

If you read the reports of what’s happening, they are ordering books by ISBN number. That’s an international system for identifying books, which was only introduced in 1970. If they’re ordering a book by its ISBN, it’s no medieval illuminated manuscript.

So the books being scanned and destroyed are relatively new, but can they still be described as rare? In that case just like anything else mass-produced since 1970, how many survive depends on the size of the original print run and how valued they have been since. So a few of these books can be physically rare in the sense of being uncommon, but if they are next-to-valueless, it’s fairly obvious nobody has particularly cared about their survival up to now. It’s likely that any books printed since 1970 which are both rare and of value will have their future assured, so the AI industry is not committing the wanton destruction of culture the reports would like to suggest.

You Need To Know Just How Many Books Get Pulped Every Year

People are often shocked when they find a dumpster full of books for recycling. Ricky Shore, CC BY-NC-ND 2.0.
I’m left feeling that a combination of the symbolism of destroying books along with a distaste for AI companies has inflated the status of these books well beyond their worth. If people truly had a care for old books they would be shocked to know how many are pulped each year by the paper recycling industry.

The publishing industry has been churning out mass-produced books for centuries now, so the world is awash with old books. Where do these newly-minted bibliophiles imagine they all go, to the Great Library In The Sky? I haven’t even touched yet upon the publishing industry, which pulps vast quantities of brand new unsold books every year. Where is the outrage, I ask?

We all love to dunk on AI companies, and Heaven knows, there are plenty of reasons to do so. Among all those reasons, sadly destructively digitising books is pretty low on the list. Please, ask the other questions, the ones they really don’t want to answer!

Header image: Yair Haklai, CC BY-SA 4.0.

hackaday.com/2026/08/25/ai-boo…

One day, people will look back at what we call Artificial Intelligence and laugh. We do the same thing today, as chat bots totally outstrip what the computer industry called AI up until pretty recently. This didn’t escape curators at the Internet Archive, apparently, and [Jason Scott] tells us about a recent collection, “Vintage Artificial Intelligence.”

These are old software titles that will run for you in emulated machines right in your browser, ranging from somewhere in the 1970s to the 1990s. There’s Eliza, of course. Actually, there are several copies of Eliza. Given how simple it was to write Eliza, it did a pretty good job. Then there are adventure games that are pretty conversational, Lisp, Prolog, which was going to spawn expert systems to replace us all, and Racter, which tried to write fiction.

There was even Alter Ego that was supposed to help you explore life decisions, maybe? There are a couple different versions of even a few versions of Conway’s Game of Life. We aren’t sure that’s ever really been AI, but perhaps it depends on your definition. We’re happy to see Sargon, the chess program, represented.

We didn’t see Hexapawn, which is a shame. We also didn’t see Parry (the paranoid counterpart to Eliza) or that elusive software we remember but can never find that built word chains from text called George.

We’ve written about Eliza before. If you want to experiment with Prolog and you like Pokémon, you’ll appreciate this tutorial.

hackaday.com/2026/08/25/artifi…

When I got back into SLA resin printing recently, I knew that I’d inevitably have to deal with the agony of failed prints and of course resin spills. This moment eventually came, and I felt motivated to treat mistakes as teaching moments on aspects like how to properly prepare an SLA build plate in terms of angles and supports or how to deal with failed print aftermaths.

Before moving on to the disaster, I’d like to first start with a look at the resin print of the previous article, which contained a number of fairly small parts. These I had oriented and supported almost fully using the automatic methods provided by the ChituBox slicer software, and worked about 90% as I had hoped, while leaving plenty of room for improvement as well.

Overall, preparing an SLA build plate in the slicer isn’t quite the same as for an FDM printer, mostly due to one phrase that strikes fear in the heart of anyone who has ever done resin printing: “peeling forces”.

Not Bad, Not Great

For last article’s resin print, I had to put a number of models onto the build plate in the slicer, after which I mashed ‘auto arrange’, ‘auto orient’ and then ‘auto support’ in their respective tabs. I did change the orientation of the beam so that it wasn’t pointing straight upward any more, as I wasn’t going to wait a few extra hours for it to print just for that single object.

This then got me the following overview including a veritable forest of supporting structures:
You’re going to enjoy peeling off those supports later.
By playing it safe, I managed to get everything printed without any glitches other than my previously mentioned fight with the resin auto-feed system of the printer. Of course, by leaning heavily on defaults, I also got backstabbed by the slicer’s overzealous use of supports, especially where it was highly undesirable, such as inside parts of the LEGO Technic-compatible parts:

By rotating the figurines to be printed upside-down relative to the build plate this also meant having lots of ugly marks left by the supports, both on the happy buddha and the female knight figurine.

Here the fix seems rather straightforward: angle figurines so that supports contact things like the bottom of a surface where it won’t be as noticeable. Also inspect the auto-generated supports to remove any that are in naughty places and perhaps do some manual supporting if you feel particularly confident.

I did look at a few “how to do supports right” videos and written tutorials, and the general advice seems to be to simply forget about auto-generated supports.

For me an amazing aspect was that both figurines were angled upside-down by the slicer, when everyone prints them with the base towards to the build plate. Exactly how ChituBox’s algorithm here works is a complete mystery to me, but I reckon that this slightly confusing experience may have contributed to the subsequent disaster that occurred with another print.

Simply Bad

The FDM version of the CD rack in black PLA passing QA.
Where things slid slideways and wrapped themselves at high velocity around a phone pole was when trying to print a 16-slot CD rack, specifically this rather nice model by [zenitar3d] from Thingiverse. On an FDM printer this is braindead simple to print: you slap it on the build plate in the slicer, do a sanity check that it physically fits, slice it and let ‘er rip. My only issue here was that OrcaSlicer deemed it necessary to add a brim, so that took some sanding to clean up a razor sharp edge.

On the resin side of things, you enter a torment nexus: you can slap the part on the build plate, but then you risk elephant foot — a thickening at the base where exposure time is longer than for subsequent layers. Even if that’s of no concern, you still need to violently remove the part from the solid metal build plate, which is highly likely to cause damage.

If I still had the LD-002R printer with its flex plate, an aftermarket modification that I had fitted. This would be of no concern with a mere flex-and-pop, but here I’d have to violently wield a metal scraper to convince the build plate and cured layers to part ways. Clearly I need to look into flexible build plates for current SLA printers.

I did try to use the same auto-angle and auto-rotate approach in the slicer, but ChituBox would just always put part of the model outside of the printing area. After a while I grew tired of this and just printed it with the part slightly lifted off the build plate with medium supports like this:
Anyone who has ever done any resin printing cringes at this screenshot.
In my defense, I did this in the midst of yet another European heatwave with zero air conditioning, so maybe that had sufficiently fried my remaining brain cells. Regardless, the results were rather predictable.

Carnage

A little while later I had the good news in the sense that the supports were printing beautifully, but also bad news in that the actual model had been ripped off the supports by the aforementioned peeling forces.
Cue sad trombone SFX.
In hindsight this was obvious: the quite solid surface of the model has significantly more surface area than the area contacted by the supports. At the first attempt to peel the newly cured model layer off the nFEP (PFA) film, the tug of war resulted in the supports winning out and the print being a total failure.

You could call this the ‘FDM spaghetti’ equivalent with resin printing, where the FDM’s extruder is printing in empty air, but unlike with FDM printing the subsequent clean-up is less of a sighing, brushing away bits of thermoplastic and trying again with the glue stick, and more of a chemical hazard situation.

Dealing with an SLA resin printing failure sees you draining and filtering the resin from the vat, carefully removing any solid resin from the vat’s film and curing the failed parts so that they can be safely disposed of. All while suited up with gloves, eye protection, and at least a half-face mask with A1P2 filters that still leave you plenty of opportunity to consider whether SLA resin or IPA smells worse when the copious amounts involved of both try to overwhelm the filters.

Clean-Up Detail

All of this is perfectly fine.
Where the whole kerfuffle got even worse was when the whole auto-feeding of the resin caught up with me. After ripping the bottle out of the machine I had noticed that the GK3 Ultra had for some reason pulled a vacuum inside the bottle, which could explain some of the issues that I had experienced. This did however also mean that its internal volume had decreased due to the bottle’s deformation.

This was a detail that didn’t quite register with me until resin that I was pouring through the filter into the bottle was overflowing onto the floor. Cue copious amounts of colorful cursing and a dash for the paper kitchen towels, followed by a rather illuminating UV exposure session using a handheld UV lamp. Fortunately cured resin doesn’t bond well to tile flooring, so it can be peeled off after curing and tossed into the regular household waste. The pro-tip here is to always use silicone underneath potential resin spills. If only I had done so.

With the floor clean once more, the next challenge was to get the vat cleaned up again. The provided silicone scraper was useful here, but you absolutely need that spray bottle with IPA to soften up the connection between the PFA film and the cured resin.
This calls for IPA and elbow grease.
Using the built-in vat curing feature I could cure most of the remaining resin in the vat, but still had to use the handheld lamp to get to corners where it didn’t reach. This is the part that I’m still working on, making sure everything is clean and the PFA film undamaged before I throw myself again at another printing session.

Lessons Learned

As they say, spilled milk, or resin.
I think the primary lesson that I have learned here is that I still do not comprehend why consumer resin printers insist on having that solid lump of metal that they dare to call a ‘build plate’ — an immovable surface that you have to violently assault with a scraper after printing to make it release printed parts.

After mostly printing with the magnetically attached flex plate on the LD-002R – of course after adjusting its Z-height correspondingly – it still feels like time hasn’t moved at all here.

As a friend of mine remarked when I reported the print failure described in this article, it’s also rather astounding that there’s no simulation of peel forces in slicers to get some idea of whether your supports game is overkill or weak sauce. There are some resin printers that even try to reduce the peel forces by tilting the vat – such as the Prusa SL1S and Form 3 – and there are various ‘tricks’ to reduce the peeling forces, such as lubricating with silicone and PTFE oil, many of which I too have tried with the LD-002R with unclear results, but ultimately you just want to ‘science’ it, as the kids say.

Overall, a resin printing failure isn’t the end of the world, as long as you are mindful of a potential mismatch between the air volume in the target bottle and the resin volume in the vat you’re pouring from. Resin is only nasty until you blast it with UV, when it turns into relatively harmless plastic.

All of that said, I’m still torn on that CD rack model. Theoretically the GK3 Ultra has the build volume for it, surpassing the Neptune 4 in two directions, but it’s not easy to prepare a plate in such a way that the model isn’t ripped off its supports, is not disgraced by a massive elephant’s foot, or worst case the build plate wins and the FEP/PFA film loses the tug of war and rips.

Did I mention rips in the vat’s film? That’s another thing I experienced with the LD-002R back in the day. I was lucky that the resin spill was fairly contained, but I was puzzled for a while why the prints kept failing until I actually drained the vat.

Anyway, after all this learning, it’s time to reorganize and see what I can improve when I next hurl myself at this whole SLA resin printing topic.

hackaday.com/2026/08/25/anatom…

The Quest virtual reality headset gets a fully unlocked bootloader thanks to the QuestStack tool, which automates a complex process of privilege escalation to provide stable, privileged access to the hardware. This solidly frees the headset from its existence as a device tied to Meta’s walled garden, although the tool only works on the Quest 1.
Image credit: notmastergamerok on Reddit
Not simple enough? No problem, there’s also a web version by [darknight1050] that makes the unlock process as simple as plug in headset, visit web page, receive unlocked bootloader.

The first-generation Quest headset is an older (released in 2021) piece of hardware that is still perfectly capable, although it has been surpassed by later models in terms of performance and optics.

It has also been essentially forgotten as far as parent company Meta is concerned, with no requirement for new content to be compatible with it, nor consideration in general given to the device for some time now.

Hardware that is no longer supported should be opened. The Oculus Go got an official unlocked OS build which was a positive thing, but the Go was also a pretty limited device. The Quest 1 — the ‘Oculus’ part of the name having been dropped around the time Facebook renamed itself to ‘Meta’ — is considerably more capable than the Go was. Now people can have privileged access to its hardware, which may help save some of them from junk piles while enabling folks to do as they please with the hardware they purchased.

hackaday.com/2026/08/25/quest-…

When the analog TV signals were turned off in most places around fifteen years ago, their replacement took the form of a set of digital multiplexes. ATSC for North America, and DVB-T for Europe and other places. This would deliver a multi-channel broadcasting solution for the future, and this would be how those not on a cable would consume their telly. It’s a surprise then to find that some governments are already looking at turning off digital TV broadcasting, with the UK in particular wanting to put a date on the switch-off of 2032.

It’s been no secret for many years that linear broadcast TV is being overtaken by streaming services, and this move projected to come at the end of the transmitting contract was always likely to come eventually. Even with increasingly few younger people watching traditional TV though, it still comes as a bit of a shock that it’s happening so soon. The replacement will be an online service for which initially a set-top-box will be required. We’re guessing there will be a storm of protest, but since it’s still quite a few years away and broadband coverage is now near-universal, there’s a good chance it will peter out as the time approaches.

Aside from the end of analog TV, we’ve seen a steady decline in AM and Long Wave transmission across Europe. What makes this surprising then is that instead of being a legacy analogue system, the one facing the turn-off is the future-proof replacement, and one that still sees plenty of use at that. A major shift in consumer electronic technology is taking place, but will anyone notice it?

Header: Carlos Adampol Galindo, CC BY-SA 2.0.

hackaday.com/2026/08/25/the-da…

Printed footwear is an intriguing idea, but as far as projects go it is somewhat more complex than it first appears. This guide to 3D printing your own clogs not only provides a solid process, but also acts as a list of the challenges and pitfalls involved. After all, a piece of footwear is actually a fairly large object. Failed prints can be costly and time-consuming, so a guide like this is a valuable resource.

First of all, a 3D printer that can handle multi-material printing is called for. The footwear itself will be printed in TPU 90A as a sweet spot for hardness, but the print will require supports and those supports will need to peel away cleanly. The solution is a shoe printed in TPU with a rigid support structure of PLA. Using two different materials in the same print with anything remotely resembling efficiency calls for either a dual-nozzle print head, or a multi-toolhead printer.
3D printing one’s own clogs can be rewarding, if not necessarily cost-effective.
Here we want to take a moment and say that while the guide itself suggests PETG is also a suitable support structure, we suspect this might only be true for the exact filament formulations used in the guide. The safer approach is to use PLA. Why? As we’ve seen in other tests, PETG has been observed to stick extremely well to flex filaments in general, whereas PLA doesn’t really want to stick to anything other than PLA. The exact formulations of TPU and PETG used in the guide might be compatible with one another, but in general we recommend sticking to PLA as a rigid support for flexible filament.

Assuming a capable printer and suitable materials are nailed down, one also needs to worry about keeping the TPU dry. It is very sensitive to moisture, which directly affects print quality. You’ll also need to dial in the settings — a gyroid-patterned infill of 15% provides the right amount of “squish”, which is most effectively fine-tuned by changing the infill pattern rather than the density.

Is it worth the time and effort and filament cost to print one’s own pair of slip-ons versus simply buying a pair of Crocs®? Maybe not, but it can still be rewarding and this guide will help minimize any failed prints in the process. And if you do get a nice print but the TPU is sticking a little too well to the build plate, reach for the isopropyl alcohol.

hackaday.com/2026/08/24/straig…

Schematic diagram of the touch-sensitive skin. (Credit: Haofeng Chen et al., ArXiv, 2026)
Hypoesthesia, more commonly referred to as numbness, is one of the more distressing ailments that can affect us humans, primarily because it reminds us of just how much we rely on our sensation of touch in daily life. From experiencing the world around us, handling objects, noticing when you just bumped into that side table again and the comforting hug of a fellow human being, touch is perhaps the most important of our senses.

In that regard the recently published research by [Haofeng Chen] et al. on giving robots a skin that can experience touch seems rather important as it would give especially humanoid robots a more natural way to interact with their environment, using feedback from touch.
Poking the artificial skin. (Credit: Chen et al., arXiv, 2026)
One of the essential parts of biological skin is that it is teeming with sensors, at a density level that provides excellent resolution as required, down to sensing e.g. small surface imperfections with one’s finger tips. Replicating this with an artificial skin for robotics has always been a problem, due to the wiring and/or reliability nightmare this poses with typical approaches. Instead of focusing on many individual sensors, [Chen] et al. focused on effectively creating the equivalent of a resistive touch screen in skin format.

The basic principle underlying the demonstrated artificial skin is electrical impedance tomography (EIT), which uses surface electrodes to form a tomographic image based on measures electrical resistivity. Core here is the flexible TPU layer with electrodes and the conductive fabric patches attached to the top TPU cover layer. The electrodes continuously measure the resistivity, with disturbances from those patches due to touch events on the cover layer altering these values. From this EIT can be used to reconstruct the location and strength of the touch event.

The results from the created prototypes were promising, with only 16 electrodes sufficing to create a fairly accurate pressure map. Hardware-wise this makes it thus quite uncomplicated, with the characterization of the TPU porosity and such along with the EIT algorithm (provided in the paper) probably being the biggest hurdles for hobbyist recreations.

hackaday.com/2026/08/24/3d-pri…

The AM29000 series of processors were AMD’s entry into the world of super-fast next-generation silicon of the late 1980s. It was a time when ARM was still a niche architecture in a British educational computer, the 68000 series was still a major player, and it was by no means certain that the x86 would maintain its position. It therefore wasn’t an unreasonable choice for someone building a high performance computer at the time, which is what [Oscar Toledo G.] and his father did. If that wasn’t enough, he went on to write an operating system for it in AM29000 assembly, complete with a GUI, a C compiler, and an up-to-date web browser for the late 1990s. The story makes for an engaging read.

It’s written across two parts, with the first looking at the computer and the early software development, and the second at the C compiler and web browser. It’s a tale of epic mastery of the machine, and something we remember ourselves, piecing together knowledge in a time before the Internet placed it all at our fingertips. Tales such as hand porting — we can’t really say compiling — C code into AM29000 machine code are completely next-level. You have to read these two write-ups, and there’s even an in-browser emulator should you want to try it.

Meanwhile, in case you think something is a little familiar here, he’s the same person who brought us a Transputer in the browser.

hackaday.com/2026/08/24/a-1990…

It’s likely that even those of us who have never picked up a guitar in our lives will recognize the sound of an electric guitar with a fuzz box effects pedal. The raspy distorted sound has been at the heart of so many very well known recordings. Behind it is a distortion circuit, or as [Bill Jehle’s Mad Scientist Guitar Lab] is here to tell us, eight different circuit topologies.

The result is a fascinating trip through the evolution of rock music through the 1960s, as he examines circuits from simple diode clippers through to frequency doublers and phase shifters. He’s provided a playlist as an accompaniment so you can even have an immediate listen to each sound. It’ll mess up our YouTube recommendations, but worth it for the informative journey.

It’s also a window into a lost period in electronics where all they practically had was the transistor, so each device had to put in the maximum work for a living. Designing circuits like these called for intimate knowledge of the device characteristics, and just how they could be safely exceeded. The video is below the break, and well worth a watch.

If clever transistor music circuits interest you, you’ll love the flawed devices that gave the Roland 808 its sound.

youtube.com/embed/ywT9Wf8vlGE?…

hackaday.com/2026/08/24/an-ele…

Many pieces of consumer electronics are build down to a price, and the corners cut show up in their performance. The Gameboy Advance from Nintendo is no exception: its audio is a PWM stream that sounds awful through the included amplifier. [Cajun Panda] has a fix though, in the form of a replacement audio chain.

It takes the form of a PCB that hooks into the pads of the removed GBA audio chip, and provides a much cleaner audio path with filtering and EQ and a class D audio amplifier. In addition there’s an audio codec and an ESP32 for Bluetooth connectivity, enabled by a long press of a GBA button and configured via a web interface on the ESP. Best of all there is no case modification, this is designed to remain as stock as possible.

Everything can be found in a GitHub repository should you wish to make your own, so if you want to bring your GBA audio up to scratch you know where to go. If you want to make it even better don’t forget, you can always upgrade the screen.

hackaday.com/2026/08/24/at-las…

If you’re blessed enough that you haven’t had blood drawn in a while, you might not have thought much about the process. You might imagine that a needle goes in, a syringe is drawn back, and the venous blood is thusly collected. Indeed, it can be done that way.

However, there is an altogether niftier and more efficient method of fast blood collection for pathology testing. It’s all about using vacuum and smart design to ease the work of phlebotomists, while maintaining a sterile and safe environment.

Vacuum, Contained

These days, if you get blood collected for testing, there’s a plenty good chance you’ll have it drawn into a vacutainer. It’s named as a portmanteau of “vacuum” and “container” because that’s fundamentally what the system relies upon. A vacutainer is a glass or plastic tube which holds a vacuum inside, sealed with a stopper. That vacuum can be used to help extract fluids to be stored inside the container—namely, blood, in most cases.
A blood draw taking place with a vacutainer. The needle unit is inserted into the vein, while the vacutainer tube is slid into the housing to draw blood out. Credit: public domain
The method of use is relatively straightforward. A vacutainer needle is inserted into a patient’s vein to access the blood. The vacutainer needle does not have a typical syringe draw. Instead, the back end of the needle sits inside a plastic housing which accepts vacutainer tubes. There is a flexible rubber seal on the back end of the needle so blood doesn’t leak out when no tube is connected.

When a vacutainer tube is inserted into the housing, the vacutainer needle pierces the stopper of the tube. The vacuum inside then draws blood from the vein into the tube for collection. When full, the tube can be removed and it self-seals as the needle comes out of the stopper. Another tube can be quickly clipped into the vacutainer needle housing to draw further blood if more is needed, without leaks or mess causing contamination issues.
A series of vacutainer tubes filled with blood for testing. The different colored caps indicate different additive content, which preserves the blood under ideal conditions for different types of testing. Credit: Tannim101
Vacutainer tubes are, by design, single use. They’re manufactured to capture a set quantity of blood for testing, based on the level of vacuum in the tube at the time it is sealed, and are disposed of after use. Labels are often included on the tubes allowing patient information to stay with the blood itself. Tubes have a shelf life, as with most medical paraphernalia, in particular since they may not maintain vacuum indefinitely.

The tubes are also typically filled with various additives in order to best preserve and prepare the blood while it awaits testing, and stoppers are color-coded to indicate this. The precise additives used are highly dependent on the testing required. A tube for a standard blood culture draw will typically be filled with sodium polyanethol sulfonate, which acts as an anti-coagulant, with growth media also present for microorganisms.

Coagulation tests will use tubes with sodium citrate inside, while a test for lead will often use a tube with sodium EDTA chelator inside. Some basic blood component tests will use a plain tube with no additives, while others are highly specific—tuberculosis testing often uses purpose-made tubes with antigen additives ready to go. Some tubes include special serum-separating agents which help with splitting blood into its component parts when shaken or centrifuged, useful for certain tests that look at different blood cell types individually.
A package of vacuum blood draw tubes, with the purple cap indicating K2 EDTA additives inside. Credit: via AmazonA vacutainer needle hooked up to a housing. The needle inside the housing typically has a rubber sheath which stops blood flow when no tube is inserted. This allows tubes to be hot-swapped for drawing multiple quantities of blood from a patient. Credit: via Amazon
If you’ve ever dared to watch while having your blood drawn in this manner, the technology can look quite swish. The tubes are easy to hotswap without leaking any blood and several tubes can be filled in under a minute once the phlebotomist has found an appropriate vein.

However, the technology is not particularly new. It was developed all the way back in 1947 by Joseph Kleiner, though other vacuum-based blood draw techniques existed previously. His goal in developing the technology was to ease patient discomfort and reduce the spillage of blood. This stemmed from his experience seeing his terminally-ill wife suffer multiple needle punctures whenever multiple blood tests were required, and seeing the mess caused when syringes were emptied into test tubes for processing and testing. His inspiration was seeing vacuum-sealed tubes used by the military to transport blood during World War II; the product he developed would later reach the market in 1949. They had the benefit of keeping the blood from exposure to air, reduced the number of punctures required along with the chance of needle stick injuries and infection, and ensured blood was collected in standard volumes and conditions, which aided clinical accuracy. Plastic versions were developed by medical supplier Becton Dickinson in the 1960s, and have become widely popular in the phlebotomy field since.

If you’re not in the medical field, and you’ve managed to avoid regular blood tests, you probably haven’t even noticed vacutainers. Alternatively, you might simply live in an area where their use is uncommon, or you’ve just been intently looking away while your blood has been drawn. In any case, they remain a neat little bit of technology that makes a messy, hazardous, medical process as clean and tidy as possible.

Featured image: “Drawing Test tubes different colors” by [Goldmund100].

hackaday.com/2026/08/24/tech-i…

One of the fun aspects of open source software is that you can often find so many libraries and tools that implement the functionality you need, but ease of use for e.g. artists is often not a priority. This is where [Edin Spiegel] ‘s annoyances with photogrammetry tools led him down to the path of creating the Simple Photogrammetry GUI project, which is basically what it says on the tin.

In an associated video its development and use is demonstrated, combining tools like Colmap, OpenMVS, mvs-texturing, pymeshlab, brush and PoissonRecon to implement both photogrammetry and gaussian splatting to turn those photos into a not too shabby mesh along with realistic textures.

The GUI uses the Flutter GUI kit, so Linux support is still somewhat sketchy, but should work in this new release of this GUI wrapper. The author is asking for people to test this GUI and report any issues found so that they can be addressed.

From a quick glance at the project and the comments to the video it seems quite useful for anyone who wants to get started quickly with photogrammetry. One niggle is perhaps that it relies on processing using CUDA, with a much slower fallback to CPU processing if you do not happen to have an Nvidia-blessed GPU installed. Of course this is one of those universal issues in a world where theoretically everyone should be using OpenCL already.

In addition to the build instructions you can also download an AppImage for Linux and compiled binaries for Windows to theoretically get started as fast as your internet connection allows. Interestingly, the AppImage is well over a GB in size, whereas the Windows ZIP file is just 207 MB for the v1.1.5 release, so take that into account.

youtube.com/embed/4wdDcGBIZ6E?…

hackaday.com/2026/08/24/combin…

Last time we found out the idea of space stations is surprisingly old. By the 1950s, everyone knew we’d be working in beautiful space stations that rotated like a wheel to give us the illusion of gravity. Of course, that didn’t happen. But we did get some practical space stations, even before the current crop. The road to get there, though, was predictably bumpy.

Convair: From TASSEL to MARS

Convair had been studying multi-person orbital stations under Krafft Ehricke since the late 1950s. One result was TASSEL, an acronym for the Three Astronaut Space System Experimental Laboratory. Proposed in 1960, TASSEL was a three-man laboratory intended for an Atlas-Centaur launch into a roughly 200-nautical-mile orbit and missions lasting two or three weeks.

Around the same time, the Air Force asked contractors for proposals for a Military Test Space Station, or MTSS. Convair was one of five companies selected for the study in 1960. The surviving record suggests that Convair’s TASSEL work fed directly into its MTSS proposal.

Then Convair did something unusual for an era overflowing with beautiful paintings of spacecraft that never existed: they built theirs. Well, sort of.

During late 1960 and early 1961, the company constructed a full-scale ground mockup called the Manned Astronomical Research Station, or MARS. The station itself was about ten feet in diameter and fourteen feet high, with two floors for working, cooking, housekeeping, and sanitary facilities. A Mercury-like reentry capsule beneath it brought the whole assembly to about 28 feet tall. You can see a contemporary video about the program below. There’s also a cache of photos and a post by [The Space Review] explaining it all.

youtube.com/embed/JWUtsvAX19g?…

MARS obviously wasn’t going to orbit, but that wasn’t the point. Engineers could use it to work on the less photogenic parts of putting people in orbit: life support, oxygen consumption, water regeneration, contaminant monitoring, controls, displays, and simply discovering whether people and equipment actually fit where the drawings said they would. Crews later spent as long as 30 hours inside the mockup.

Exactly where MARS fits among Convair’s various proposals is still being pieced together. Archival evidence indicates that it grew out of TASSEL and closely overlapped Convair’s submission for the Air Force MTSS program. Photographs in the San Diego Air and Space Museum archive are even identified as “MTSS/MARS.” Whatever name was on the proposal of the week, by 1961 Convair had progressed from drawing space stations to building a high-fidelity example on the ground.

Olympus and MOL

Olympus was nearly 140,000 pounds, 150 feet wide, and each arm provided 35,000 cubic feet (NASA).
NASA wasn’t far behind. In 1962, Edward Olling at the Manned Spacecraft Center proposed Project Olympus. It would have been an 18-person station intended for launch around 1966 or 1967. It wasn’t the classic doughnut. Instead, three long arms extended from a large central hub, and rotation would provide different artificial-gravity levels at different distances from the center. The station would orbit about 300 nautical miles above Earth.

This is especially interesting because Olympus wasn’t a far-future colony study. It was being considered while Mercury was still flying. Then President Kennedy gave NASA a somewhat more pressing assignment involving the Moon.
Olympus joined the large pile of spacecraft that looked great in presentations.

The U.S. Air Force had another station that got considerably closer to hardware: the Manned Orbiting Laboratory, or MOL. Approved in 1965, MOL would have put two military astronauts into a polar-orbiting station attached to a modified Gemini spacecraft (Gemini B). Its actual classified purpose was high-resolution reconnaissance. You can see some silent footage of some of the hardware in the video below.

youtube.com/embed/SZVyHL6_gxQ?…

They selected astronauts. They built hardware. They modified a Gemini capsule with the unnerving idea of putting a hatch through its heat shield so the crew could crawl into the laboratory behind it. MOL was canceled in 1969 without a crewed station ever flying.

Meanwhile, docking — one of the basic tricks required to make stations useful — was becoming real.

Dock of the Bay

On January 16, 1969, Soyuz 4 and Soyuz 5 docked in orbit. There was no pressurized tunnel connecting them. So Yevgeny Khrunov and Aleksei Yeliseyev put on spacesuits, climbed outside Soyuz 5, traveled across the docked spacecraft, and climbed into Soyuz 4. Two spacecraft had effectively become a tiny space station, but changing rooms required going outside.

Apollo 9 flew less than two months later and provides an interesting parallel. The command module and lunar module could dock, and crews could normally transfer internally. But what if the tunnel couldn’t be used? NASA planned to demonstrate a contingency EVA transfer from the lunar module to the command module.

Rusty Schweickart was supposed to perform the exercise, but space sickness caused NASA to shorten his EVA. He tested the lunar EVA suit and portable life-support backpack from the LM porch while Dave Scott partially exited the command module, but the complete external transfer was never performed.

Salyut and Almaz

On April 19, 1971, the Soviet Union launched Salyut 1, the first actual space station. The first crew failed to dock successfully. The second crew, Soyuz 11, spent more than three weeks aboard, but all three cosmonauts died during reentry when their Soyuz depressurized. There is some video from Salyut 1, but no audio.

youtube.com/embed/hWUJi4uhreg?…

The Salyut name also concealed a second program. Some of the stations were civilian Salyuts, while others were military Almaz reconnaissance stations similar in purpose to MOL. Salyut 2, 3, and 5 belonged to the Almaz line, although Salyut 2 failed before a crew could arrive.

Later Salyut stations gained a second docking port. That was a huge improvement because Progress cargo ships could bring supplies and fuel while a Soyuz remained attached as the crew’s ride home. Long-duration spaceflight was becoming practical rather than heroic improvisation. Of course, none of them rotated.

Skylab

Skylab as the last crew says goodbye (NASA).
The United States took a different route. Skylab was essentially an enormous converted Saturn V upper stage. Launched in 1973, it gave its crews something previous spacecraft had lacked: room.

Three crews occupied Skylab, staying as long as 84 days. They conducted solar astronomy, Earth observations, medical studies, and experiments designed to determine what happens when human beings spend months rather than days in weightlessness. After all, why build a giant rotating station if people could simply learn to live without gravity?

Then again, we learned that long-term microgravity isn’t free. Bones, muscles, cardiovascular systems, eyes, and assorted other bits of the human body complain when they don’t have proper gravity. Still, a nonrotating station was far easier to build, so rotating wheels stayed on the drawing board.

Freedom Isn’t Free

By the 1980s, NASA was ready to try again. In his 1984 State of the Union address, President Ronald Reagan directed NASA to build a permanently occupied space station within a decade. What eventually became known as Space Station Freedom was supposed to be a large modular facility assembled by the Space Shuttle.

It would support research, Earth observation, satellite servicing, and eventually serve as a staging point for missions beyond Earth orbit.

Freedom went through redesign after redesign as costs and requirements fought each other. It did not rotate. While NASA redesigned Freedom, the Soviets quietly launched something considerably more important.

Peace In Orbit

Mir seen from STS-89 (NASA).
On February 20, 1986, the Soviet Union launched the core module of Mir.

The name means “peace,” although the Russian word can also mean “world.” Unlike the earlier Salyuts, Mir was designed from the beginning as a modular station. Additional laboratory and equipment modules arrived over the years and docked around its core.

It looked nothing like Noordung’s wheel. It looked more like somebody had been assembling an enormous machine in a garage and kept finding useful places to bolt things on.

Mir represented decades of incremental Soviet experience: Soyuz, docking, Salyut, Progress, long-duration crews, orbital repairs, and modular construction. It demonstrated that a space station could become not merely a spacecraft but a place — one that crews could maintain, modify, repair, and inhabit for months at a time.

Where’s My Wheel?

That may be the most surprising thing about the history of space stations. The rotating station wasn’t some goofy 1950s science-fiction invention. Serious engineers were proposing artificial gravity before anyone had launched anything into orbit. Oberth discussed rotating stations in 1923. Noordung drew a remarkably complete wheel station in 1929. Von Braun made the concept famous in the 1950s. NASA seriously studied rotating stations in the 1960s. The physics works.

We’ve simply never needed artificial gravity badly enough to pay the cost.
If you can tolerate microgravity, a station can be a collection of pressure vessels, trusses, solar arrays, and docking ports. If you insist on one g at a comfortable rotation rate, suddenly you are contemplating a structure hundreds or perhaps thousands of meters across.

Still, Edward Everett Hale put people aboard an artificial moon in 1869. Noordung put them aboard a rotating wheel in 1929. Kubrick had airline passengers walking around one in 1968. So after more than a century and a half of talking about space stations, I have only one question: When do I finally get my rotating space station?

hackaday.com/2026/08/24/an-ear…

IT'S MONDAY, AND THIS IS DIGITAL POLITICS. I'm Mark Scott, and hope many of you are heading back to work after a restful (if hot) summer break. There's a lot to dig into for the Fall — buckle up.

— French lawmakers and US tech companies don't agree on much. But both believe efforts to protect children from harm on social media are undercooked.

— Washington is re-using its TikTok playbook to go after Chinese open-weight AI models. That does a disservice to the artificial intelligence industry in the United States.

— Roughly one-third of the English-language webpageshave been written or edited via AI since OpenAI released Chat-GPT in late 2022.

Let's get started:

digitalpolitics.co/social-medi…

Not the prettiest ruby, for sure. (Credit: Gems of Science, YouTube)
Sapphires and rubies aren’t just pretty, they also got a range of practical uses. This makes it even more useful to be able to make them at home for obviously completely innocent experiments. Cue [Gems of Science] and his attempts to make good-looking rubies, without resorting to the brute-force laser blasting approach that [Styropyro] previously used to create murky-looking gems.

That basic method used involves blasting aluminium oxide with a laser, which results in a container full of what are technically gems, but – as the image on the right makes clear – not exactly the prettiest or easiest to shine up. Much of the problem here is that these are hollow geodes composed of countless tiny crystals instead of solid singular crystals.

Although there are commercial ways to fairly easily create large crystals from a small seed crystal, none of these lend themselves to a DIY hobbyist with just a garage to muck about in. This leaves one alternative: the flux method. Rather than melting the material that will be grown onto the seed crystal, this flux crystal growth method uses a solvent (flux) and temperatures that a home kiln can achieve.
These rubies may be small, but are very shiny. (Credit: Gems of Science, YouTube)
Of note here is also that it’s the addition of Cr³⁺ ions into the base Al₂O₃ matrix that makes a ruby into a ruby, by giving it its red glow. In order to grow crystals this way you need to pick not only a suitable solvent, but also use a crucible that doesn’t want to become part of said crystal. Unfortunately a platinum crucible runs into the thousands of USD, but a graphite crucible should do if you keep oxygen away from it.

For the flux molybdenum oxide was used, mixed with chromium oxide and aluminium oxide to provide the ingredients for crystal growth. Unfortunately added charcoal interfered with the molybdenum, ruining that batch. This led to trying out more crucible types to find a recipe that worked, thereby finding out that an ‘alumina’ crucible also contained silica, which poisons the reaction, resulting in only tiny ruby crystals.

Ultimately pure alumina crucibles seemed to work great, until they began to shatter en masse, resulting in pained wallet noises and the purchases of some pre-loved platinum crucibles. This worked really well, but now the flux was evaporating too quickly to enable large crystal growth, thus requiring additives to stabilize it. Along with temperature cycling to induce the growth of larger crystals, this finally generated some solid results. After a first batch of smaller rubies, next up larger ones of up to 10 mm were grown.

While cutting one of these large rubies to set into a ring it was clear that it was still rather flawed, with pockets of flux captured into the crystal, but with the basic method now more or less dialed in it should be possible to address these small flaws as well.

youtube.com/embed/2E6yW2bTLys?…

hackaday.com/2026/08/24/making…

The Casio F-91W digital watch is perhaps one of the most successful pieces of consumer electronics ever made, having quietly supplied the essential function of an inexpensive and accurate LCD digital timepiece for many decades. As a result it has a huge following, and we’ve seen plenty of projects based upon it. [Matteo P] has one that we think you’ll like, he’s turned his Casio into a contactless payment device. We missed it when it came out, but sometimes a good project needs sharing.

If you’re a long-time Hackaday reader you may remember our investigation of 13.56 MHz NFC cards in which we showed you a disassembled card in which he antenna was a tuned circuit covering most of the card, with a small coupling coil for the chip. It’s this kind of card he uses, and ends up with an SLA printed front face for the watch that places the chip above the display and puts a pick-up coil around the outside. The most interesting part of the write-up though isn’t in the build, instead it’s the deep-dive into designing the RF parts and ensuring a good coupling at something close to resonance. Read it, if you fancy trying NFC-enabling any other random items.

Meanwhile, if this NFC bug has caught you, don’t forget our rather silly one transistor 125kHz NFC reader challenge.

Thanks [John Elliot V] for the tip!

hackaday.com/2026/08/24/the-ca…

Using the special pens to remove the wax coating on the template. (Credit: Old Typerwriters and Calculators, YouTube)
Document duplication has been a highly desirable feature, long before medieval monks slaved over yet another illuminated manuscript by flickering candle light. Fortunately one part of the Industrial Revolution was the invention of machines like Cyclostyle copying machines, which covered a range of manual and automated devices. One such crank-powered device from 1890 is demonstrated in this video.

The Cyclostyle and neo-Cyclostyle copying system was quite simple yet elegant: by removing the wax coating on a special piece of paper ink from a screen-printing system could be pressed through the resulting template, and allow for repeat copies to be made.

With the machine demonstrated in the video the ink is applied to the top rollers, with the lower roller inking itself on them during the retraction cycle, before applying the fresh ink to the screen on the cycle following the insertion of a fresh piece of paper to print on. With this method many copies of the design on the waxed template could be made before it had to be replaced, which would have saved countless hours of work by artists.

After the machine in the video more advanced designs were developed, some of which we covered previously. These would automate more parts of the process, making it faster and more precise, before being replaced by newer technologies.

youtube.com/embed/J498SiIho1Y?…

hackaday.com/2026/08/23/neo-cy…

It’s arguably adult-sized. (Credit: Sam Barker, YouTube)
A staple of old movies featuring railways, many handcars – also called pump trolleys or pump cars – feature the characteristic seesawing beam. Requiring at least two people, the motion of this beam is subsequently converted into the rotating motion of the wheels, propelling it at a leisurely pace across the tracks. As a fun and yet functional mechanical contraption it also makes for an entertaining 3D printable project, which is what [Sam Barker] and [Tom] did.

You can find the entire project over at Printables if you are feeling the itch as well, though as of writing details on the required bolts and shafts are still pending.

Since the entire assembly had to be lugged over to the Open Sauce event in the US, they had to design it to be small enough to fit into check-in luggage and easy enough to reassemble in a hotel room. Naturally this put some constraints on the full size of the contraption, with it omitting compatibility with standard gauge railways and also being decidedly fun-sized.

That said, it seems to have left an impression on the folk over at Open Sauce, and it’s hard to argue with the sheer fun factor of such a co-op mode of transportation. Even if bicycle-style handcars are more popular these days, especially for tourist purposes, the old seesaw-style has that certain charm to it.

youtube.com/embed/tVi0EMVj3_8?…

hackaday.com/2026/08/23/3d-pri…

We’ll start this week off with some disappointing, though not entirely unexpected, news — the ambitious commercial mission to save NASA’s Neil Gehrels Swift Observatory is officially a bust. The space agency provided an update earlier this week explaining that the attitude control issues with the LINK spacecraft that started a few weeks after it launched will prevent it from being able to safely dock with the Swift Observatory and boost its altitude. As such, the space telescope is now expected to reenter the Earth’s atmosphere and burn up before the end of the year.

Although LINK won’t be able to live up to its name, NASA did say operator Katalyst Space has been given permission to continue with the rendezvous attempt. The two craft won’t actually make contact with each other, but teams on both sides feel there’s lessons to be learned and data to be collected by seeing the orbital dance of these two vehicles play out for as long as possible.

Speaking of hardware that couldn’t quite hit its design goals, TechCrunch is reporting that a class action lawsuit has been filed against Oura by customers that say the company made misleading claims about the sleep-tracking accuracy of their smart rings. Namely, that the rings could somehow detect which stage of sleep the wearer was in with only the pulse and temperature sensors it has onboard.

The complaint argues that sleep stages can only be accurately determined with an electroencephalogram (EEG), and that there’s no way for the ring hardware to actually know what’s happening in the wearer’s brain. For their part Oura has released a statement defending their methodology, and say that the ability of their rings to estimate sleep cycles compares favorably with data collected from clinical sleep studies. It should be interesting to see how this one plays out.

On the subject of products not quite doing what you expected, there’s been a story buzzing around online about a number of computer games failing to work properly on Windows machines that have installed the August system updates. Microsoft has investigated the issue and is currently pointing the finger towards RGB lights as the potential culprit.

On the surface it might sound like some kind of exotic hardware clash or interference, but the actual issue is disappointingly mundane. According to Microsoft, the August update fiddles with a system component that the software which drives some of these lights ties into, namely inpoutx64. As a quick fix they’ve provided some instructions on keys that can be modified in the Windows Registry to prevent the conflict, but it sounds like such gefingerpoken und mittengrabben may prevent the blinkenlights from performing their critical function.

Finally, we’ll end this week with an update on the ASCII CITY project that’s been making the rounds online. For those who haven’t seen it yet, this is 3D engine implemented in a single HTML file that renders a cyberpunk 3D city for players to wander around in. The latest version brings many new features to the non-game, notably the ability to enter the various buildings scattered throughout the world.

youtube.com/embed/UCKEDWowc0o?…

Previously we could only admire this virtual world from afar. But now that developer Grow Now! Games has released a playable prototype, you can transport yourself into this new digital frontier like in Tron.

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/08/23/hackad…

After previously putting a very basic version of Minecraft on the Game Boy Color, [Tobi] decided to have some fun and port that version also to the Super Nintendo (SNES), just to see what would happen with its more powerful hardware. Even without using an add-on chip like the Super FX 3D chip that made games like Star Fox and Doom possible with its 3D-rendered geometry, the basic SNES hardware can already provide a serviceable Minecraft experience.

You can download the SFC file here, featuring a starting world in which you can do all the usual Minecraft-ing shenanigans, like world destruction and construction. Unsurprisingly the game’s resolution is much higher than on the GBC, though the brief glimpse [Tobi] shows of Minecraft on the Game Boy Advance (GBA) with its proper 3D-rendering hardware are leaps ahead of what the basic SNES can do.

This of course raises the question of what Minecraft on the SNES could look like once you add the Super FX or similar 3D accelerator chips for the SNES into the mix. Rather than just being limited to sprite-based graphics and transformations, suddenly you can use real polygons.

youtube.com/embed/qva2Og5PP_8?…

hackaday.com/2026/08/23/using-…

Impressive as it most certainly is when an amateur fabricates a semiconductor, most of the projects we’ve seen are more demonstrations than workable chips. [Dr. Semiconductor], however, is going much further with his fabrication process, and is already working on a method to bond chips to printed circuit boards. It’s difficult to align a PCB with the pads on the underside of an opaque silicon wafer, however, so as a trial run he’s made and bonded some transparent LED chips.

The starting material for these chips is a gallium nitride (GaN) LED epiwafer, a stacked structure of n-doped GaN, an indium gallium nitride quantum well layer, and p-doped GaN grown on a sapphire substrate. When current passes through the structure, electrons from the n-doped layer and holes from the p-type layer recombine in the quantum well layer, emitting blue light. To make a functional LED from this, [Dr. Semiconductor] needed to make electrical contacts to both the n-type and p-type layers. Making the n-type contact required cutting through the p-type and quantum well layers.

This would normally be done with reactive ion etching in chlorine, but [Dr. Semiconductor] came up with a new process: a 355-nm ultraviolet etching laser causes GaN to break down into gallium and nitrogen, with the resulting cut being cleaned up by a potassium hydroxide etch. To deposit the contacts themselves, [Dr. Semiconductor] formed a photoresist mask, deposited metal (nickel, silver, and titanium) in a sputtering chamber, and used a developer solution to dissolve the mask and lift off the unwanted metal regions.
The LED after bonding and phosphor application.
When [Dr. Semiconductor] applied current between the two contacts, the LED glowed bright blue. The next step was to mount it to a PCB; to do so, he first sliced the wafer into individual LED chips with the ultraviolet laser. He then electroplated indium bumps onto a printed circuit board, positioned the chip above these bumps, added some rosin flux, and melted the indium bumps. This soldered the chip to the board and let the board power the LED.

Like most commercial LEDs, these were blue; most LED assemblies additionally include a phosphor layer which absorbs blue light and emits another color. To create a white LED, for example, [Dr. Semiconductor] mixed cerium-doped yttrium aluminium garnet phosphor power with clear silicone and spread it over the LED. This absorbs some of the blue light and emits yellow light, and the resulting mixture of blue and yellow light looks white to human eyes.

We’ve previously covered some of the history of LEDs and the phosphors which make them useful. This seems to be the first inorganic LED we’ve seen, but we’ve also seen a few homemade OLEDs.

youtube.com/embed/VHyoz8fFpUM?…

Thanks to [SpuriousIndices] for the tip!

hackaday.com/2026/08/23/making…

There’s no actual data, but if we had to guess the least-favourite Disney movie of former Amiga owners would have to be Frozen, because none of them will ever be able to “Let it Go”. The Amiga-derived AROS Research Operating System has just been ported to boot bare-metal on the Raspberry Pi, in both 32-bit and 64-bit versions. Yes, there’s a 64-bit Amiga-compatible OS that runs on ARM. It truly is a time of wonders.

AROS has already been ported to a number of platforms. Besides x86, there’s a PPC port that provided a lot of code to the MorphOS, which you can read about here, and a back-port that brings AROS back to original Amiga 68k hardware. There is even a build for RISC V.

AROS developers are making sure that Amiga legacy isn’t stuck on any given hardware, so they never have to let it go. So while not totally out of left field, this development is “pretty nifty” both in that it gives another ultralight operating system for the Pi, with boot times to rival RiscOS, and another platform for ex-Amiga users to play with that isn’t 40 years old. Previously if you wanted to run AROS on a Pi it was virtualized in Linux, making it similar to all other Amiga emulators.

While some software has been recompiled for ARM, the available software isn’t as full-featured as x86, but that’s almost certain to change as time goes on. It’s early days yet and this build is very much a work in progress. Likewise we expect support for other Pi boards to expand, as while right now the target is the Pi3, the forum threads include discussion of the Pi4 and even Zero2W.

You can check the port out in action in a video by [Dan Wood] embedded below, sent to us by tipster [Stephen Walters]. Thanks [Stephen]!

We have featured AROS once before, thought it’s been a while.

youtube.com/embed/X4fmWAIv7FE?…

hackaday.com/2026/08/23/amiga-…

Like a lot of us [Liam Kloppers] had a problem with doomscrolling. Unwilling to go cold-turkey because he does find some utility in social media. He tried a number of things before deciding to say “Screw it” and just go full Pavlov on himself with some old-fashioned classical conditioning. Who needs willpower when you have electric shocks to dissuade you?

The key here was finding an electric-shock dog collar that could be controlled via a smartphone application, which meant he could reverse-engineer its Bluetooth protocol and get it linked up to his own software. The initial implementation ties his quick-and-dirty Python control program with a web server living on his laptop, which he’s configured MacroDroid to call on when his personal criterion for ‘doomscrolling’ is met.

With the shock collar wrapped around his leg, [Liam] was ready to test. It turns out dogs are a lot tougher than people, because even when set to a low level, the shock from the device made him toss his phone across the room and had him hesitant to even pick it up again.

Since he couldn’t bring himself to put the shock collar back onto his leg, he’s now thinking of an audible alarm, something we’ve seen work before. If you’re as unhappy with your habits as [Liam], perhaps consider a device like Commodore’s social-media-free phone before resorting to self-electrocution.

hackaday.com/2026/08/23/blueto…

It’s quite likely that many readers will have harbored dreams of owning, or at least driving, a steam engine of some kind. [James Hervey-Bathurst] was lucky enough to do so in a time when it was still possible to find scrap steam-powered machinery for restoration, and at the recent Electromagnetic Field event in the UK he took the time to describe his journey from finding an abandoned steam lorry in a Buckinghamshire field in 1975, to a few years later, taking it to the road.

The talk starts with the story of its retrieval, then the long process of rebuilding, and finally its first run. He’s the owner of Eastnor Castle, the ancestral pile that serves as venue for EMF Camp, so we’re guessing that having somewhere spacious for such a project must have helped. Along the way, we get a comprehensive run through the workings of a 1920s steam vehicle, from its double-expansion compound engine to its three-speed gearbox, stopping for small details like its injectors, and a curious exhaust steam heater designed to reduce the clouds of visible steam.

Most of us will never get the chance to take the wheel of a Foden such as this one, but at least we’ve had a chance for a closer look thanks to EMF. The full video is below the break, meanwhile if you’d like more on steam injectors we have you covered.

media.ccc.de/v/emf2026-286-1-t…

hackaday.com/2026/08/23/so-you…

A time-honored tradition in the electronics repair business is to make many into one, specifically a stack of broken devices into one that works. So too with a triplet of heavily corroded and bug-infested WiiMote controllers that [eWastelander] dug out of a box of e-waste. After suffering abuse like leaving in leaky alkaline cells, bugs and general corrosion the task was to see whether at least one working WiiMote could be assembled from these three. (Video, embedded below.)

Adding to the fun was that the PCBs in these WiiMotes spanned at least two hardware revisions, and on one board the battery corrosion had caused an IC to fall off. After an initial assessment, neutralizing the battery acid and a deep clean of all the disassembled parts, it was time to give it a shot at reassembly into something resembling a Wii controller you could use and even want to touch without washing your hands afterwards.

Ultimately at least one working WiiMote was put together, with still an open question whether the remaining two units in much worse conditions could be revived in some way. An interesting idea here is to use the WiiMote shells for a custom OpenMote board, which replaces the guts with an ESP32-S3-based system for more general non-Wii things around the house.

youtube.com/embed/o6_nkWCBvjY?…

hackaday.com/2026/08/22/turnin…

Over recent years there have been a range of classic 16-bit consoles coaxed into running familiar operating systems, with -nommu Linux being a favourite. But the 16-bit era had its own operating systems of note, and [1d4r3k] has brought one of them to a console that fit very much into a different 16-bit camp. It’s Atari’s TOS, on a Sega Mega CD.

We should in all fairness start by saying it’s not “real” TOS, but EmuTOS, an open-source drop-in replacement. So far it supports a serial keyboard device, a printer, and sound, and it mounts the CD or cartridge it booted from, a RAMdisk, internal backup RAM, and cartridge save RAM. We’re told in the tip email that there’s also been some work porting GEOS to the platform, and thus the GEOS software suite may be ported to it.

Sadly there are no images, so we can’t see it working, but trying it looks to be as straightforward as burning aan ISO or flashing a cartridge if you have the original hardware. We have no idea as to whether it would be any use given the specs of the Sega, but given that TOS ran on Ataris without a lot of RAM we suspect it might be. Meanwhile, here’s a Megadrive/Genesis running Linux.

Header: 軍事用懐中電灯, CC BY-SA 4.0.

hackaday.com/2026/08/22/an-ata…

Drone control links are, from a radio signals perspective, nothing short of amazing: using a transmitter capable of transmitting, at most, one watt, a protocol such as ExpressLRS (ELRS) can control a drone over 100 kilometers away. [Stan], who has been building a drone electronics stack from scratch, recently designed four ELRS receivers and went over the principles behind their incredible range.

Up to a certain point, the simplest way to increase a radio’s range is to lower the frequency; lower radio frequencies penetrate better through most materials and don’t attenuate as quickly with distance. However, although ELRS can use 900 MHz bands, [Stan]’s receivers primarily use 2.4 GHz. The major improvement is in modulation: unlike other control protocols, which mostly use frequency modulation, or Wi-Fi, which uses phase and amplitude modulation, ELRS uses Chirp Spread Spectrum modulation. This has a low data rate, but it’s very reliable; every bit is transmitted as a chirp – a linearly rising radio tone – and the data is encoded in the chirp’s starting frequency. To decode this, the receiver multiplies it with an inverse chirp, then takes a fast Fourier transform, revealing the starting frequency. This process has an equivalent gain of 24 dB, which is enough to let it decode signals even below the receiver’s noise floor.

The hardware [Stan] designed to implement this was comparatively simple, just an ESP32 microcontroller, an SX1281 radio chip, and a few peripherals. All four receivers worked in 2.4 GHz, but two had additional 900 MHz antennas. Against RF design convention, one of the receivers used a via to connect the antenna. This would normally cause a significant impedance mismatch, but since there were enough ground-plane vias nearby, the current return path was barely affected; the receiver’s performance hardly changed. In one test, all four receivers maintained a connection at more than five kilometers, despite a forest blocking the signal’s path.

We previously covered ExpressLRS when it was still an emerging technology. To get this kind of range, it builds on LoRa technology, which has reached some impressive distance records.

youtube.com/embed/ssmQkRkXE84?…

Thanks to [Keith Olson] for the tip!

hackaday.com/2026/08/22/open-s…

Making a film camera is a project within the reach of almost anyone, from the experimenter with cardboard and sticky tape, to the machinist with an aluminium billet. But 3D printing has opened up the world of cameras to whole new set of experimenters, and we’ve seen some very impressive builds here as a result. For all that, there’s always been a particularly tricky aspect to a home made camera: the shutter. In particular, making one with variable speed has proved almost impossible. Now [Camera Things] has given it a very good shot, with a sliding 3D printed design.

To cock it, both the strips are pulled across, before the blind strip is pushed back, and the shutter operates by sliding back under the influence of a rubber band. The clever part in this case is that the blind strip can be partially pushed back to affect the size of the shutter opening. The effect is then of a variable width strip of light passing over the film, which is equivalent to varying the speed of a conventional shutter.

Due to space constraints he’s only able to make it a half frame shutter, so he’s abandoning this design in favour of a more complicated set of vertical leaves. Sadly he’s not made the files available, but we thing proficient CAD users should be able to make their own version. The video is below the break.

It’s not the first printable shutter we’ve seen, but it remains the first variable one.

youtube.com/embed/6xghEQB88wc?…

hackaday.com/2026/08/22/the-sh…

If you’ve got a cheap ham rig, it might not be very practical for you to receive certain transmissions out of the box. However, if you were to hack in a convenient little beat frequency oscillator (BFO) to your rig, then you’d be up and running. Here’s a simple way to do just that with a venerable old part everybody knows and loves.

The build in question concerns the use of a 555 timer IC. It’s seasoned with the right smattering of resistors and capacitors to taste, producing a 455 kHz beat frequency oscillator. This can be injected into the intermediate frequency chain of a receiver, making up for the lack of a steady carrier wave when receiving continuous-wave and single side-band suppressed carrier transmissions. Thanks to a potentiometer in the circuit, it’s tunable, too, from 455 kHz, plus or minus twenty percent or so. Thanks to the versatility of the 555, it’s possible to run the chip on a wide voltage range, anywhere from 4.5 volts to 16 volts, which makes it easy to install in just about any old radio set without requiring adding a specialized power supply. There’s also an alternative design that EDN covered in greater detail some time ago.

If you’re eager to dive into a wider range of transmissions than your radio can currently receive, this old-school ham hack could be just what the shack ordered. We feature plenty of good ham hacks around these parts, and don’t forget—we always want to hear about the freshest ones on the tipsline.

hackaday.com/2026/08/22/555-ma…