Space Cadet Pinball on Linux & Idempotency beyond replay caches - Hacker News (May 10, 2026)

Let’s start with software preservation, because it’s having a bit of a moment. A community reverse-engineering effort has brought the classic Windows XP game Space Cadet Pinball to Linux, with a port built from reconstructed source code. In practical terms, it means you can install it like a normal app—there’s even a Flatpak that bundles the game resources—rather than treating it like an untouchable museum piece. What makes this interesting isn’t just the nostalgia. It’s the reminder that portability lives or dies on two things: having source code you can adapt, and having assets that still exist and are usable. The write-up also doesn’t dodge the uncomfortable part: those original game data files are copyrighted, and “it’s old” isn’t the same thing as “it’s free.” The author floats an escrow-like idea—if software is no longer sold, it could become open-source—aiming to balance long-term maintenance with creators’ rights. It’s not a solved problem, but it’s the right tension to surface.

Sticking with preservation, the Internet Archive is expanding its footprint with a new nonprofit foundation: Internet Archive Switzerland, based in St. Gallen. The headline is geographic, but the substance is strategic. The Swiss org is meant to operate in its own national context while helping preserve endangered archives globally—think collections that can disappear due to conflict, neglect, or simple bit-rot. And there’s a timely twist: it also wants to capture outputs from the current generative AI wave, which is another way of saying, “We should archive today’s digital culture before it slips away.” In partnership with the University of St. Gallen, it’s supporting early work on archiving AI models themselves—something that’s technically and legally thorny, but potentially crucial for future research and accountability. A distributed network of preservation groups also makes the Archive’s mission more resilient, especially as legal and political pressures vary country to country.

Now, a story for the builders—especially anyone shipping APIs that can’t afford to double-charge, double-send, or double-create. A new piece argues that idempotency for side-effecting APIs is much harder than “store a response and replay it when you see the same Idempotency-Key.” In real systems, retries aren’t always clean replays: requests can overlap while the first one is still running, upstream services can time out after performing the action, and clients can mistakenly reuse the same key with a different request body. The core recommendation is blunt and useful: if the same scoped key comes back with a different canonical command, treat it as a hard conflict—like an HTTP 409—so client bugs don’t turn into silent, expensive surprises. Under the hood, that implies a durable idempotency record that captures who the key belongs to, what operation it represents, the normalized intent of the request, and whether it’s still in progress. Why it matters: idempotency is ultimately about business outcomes across boundaries—payments, ledger entries, notifications—not just HTTP neatness. If you don’t design for unknown states and downstream deduplication, your “retries are safe” promise is mostly wishful thinking.

In a very different corner of engineering, there’s a new open-source project that’s equal parts stunt, education, and cautionary tale: a macOS web server written entirely in ARM64 assembly, using syscalls directly—no libc. The point isn’t that anyone should build production servers this way. The point is that it makes the layers visible. When you write close to the kernel, you get a crisp lesson in what an HTTP server really needs to do—and you also inherit a sharper version of all the usual problems: security hardening, careful input handling, and the reality that “portable” becomes a lot harder when you’re leaning on platform-specific syscall conventions. It’s the kind of project that can make you a better programmer, even if the biggest takeaway is renewed respect for boring, well-tested libraries.

On the human side of building software, there’s a personal essay about “task paralysis”—not overthinking the plan, but feeling unable to start even when the plan is clear. The author suspects it may relate to ADHD, though they’re not diagnosed, and describes a practical role for generative AI: not as a replacement for thinking, but as a jump-start. For coding projects, getting a first working draft can shrink the distance between intention and momentum. But the essay also flags a newer risk profile: usage-based AI can create a tight feedback loop—fast results, a dopamine hit, and then the temptation to keep buying more tokens to keep that feeling going. It’s a grounded reminder that “AI productivity” isn’t only a workplace story; for some people it’s also about behavior, attention, and spending patterns.

Finally, a detour into history that still feels oddly relevant to modern systems. Emerich Juettner—an immigrant living in poverty in New York—counterfeited one-dollar bills starting in the late 1930s. The bills were crude, and yet he evaded capture for years largely because he stayed small: he circulated few notes, and people didn’t scrutinize ones. What stands out is the mismatch between the scale of the crime and the scale of the response. The Secret Service invested heavily in what became its biggest and most expensive counterfeiting investigation at the time, because the pattern was persistent but the signal was faint. He was eventually caught through chance—after a fire, kids found plates and fake bills among discarded items. It’s a case study in how systems designed to catch big, loud fraud can struggle with quiet, careful abuse—and how investigative costs can balloon even when the underlying scheme is low-budget.