Really nice work! From skimming it, it seems really well written. I'm looking forward to reading through the whole thing. I like how you contextualized how the different versions of the game were written and included primary source documents. The visual diagrams are also neat and help your explanations. If you're interested in even more Tempest source code, the code for the MS-DOS version of Tempest 2000 is publicly available here. https://archive.org/details/tempest-2000-dos-source-code I haven't tried building it myself, but from skimming through the files it seems to be intended for Borland Turbo Assembler in ideal mode.
You can use the Kindle without an Amazon account if you're fine with loading all your books over USB. It will give you a nag pop-up telling you to log in each time you go to the main menu, but the pop-up doesn't show up while you're in a book so it's not a big deal.
You will still be able to use it if you factory reset, but you won't be able to register it to an Amazon account or download any of your DRM'd book purchases. The Kindle will still work and you'll still be able to read books you load over USB. The one annoyance is there's a nag pop-up telling you to register your Kindle, but it only shows up in the main menu and not when you're in a book.
The actual reason is likely that all of these Kindles only support azw3 format ebooks, which are easy to strip the DRM from. This lets Amazon switch to only serving ebooks in kfx format, which are encrypted and harder to strip the DRM from. Amazon stopped allowing saving ebooks to your PC last year, likely for the same reason.
It definitely is frustrating though. I have an iPod from 2009 where the battery and hard drive still work fine, and I'm able to use the latest version of iTunes to sync my music and podcasts to it. Shoutout to Apple for that.
It's more complicated than that. KFX was not encrypted differently than AZW, it's just a proprietary format that no one else supports (AZW being more or less MOBI with some tweaks). The DRM and the format get conflated because the same enthusiasts who want to strip DRM tend to want ebooks in an archivable, portable, standard format that was not achievable with KFX (no other ebook readers care to implement the kind of features it supports, and the way it works is antithetical to coverting it to the more conventional formats). You could still download and strip DRM in versions of Kindle for PC that pulled the KFX format. Only recently did it get to the point that versions of the app supported by the DeDRM plugins weren't allowed to download new books.
They probably could do it in an update, but the devices where support has been dropped haven't had firmware updates in 7 years (and that was a certificate update, the last nontrivial update was over 10 years ago), so I guess they don't consider restarting firmware development to be worth it.
It is not like stripping DRM from Kindle books was the only available avenue that could halt the pirate ebook system. Moving the entire ecosystem to the format is still going to see all of the same material available on the high seas.
Worst case, the eye analog hole will ensure that books are the most piratable medium.
there is something bitterly ironic about iPods (and their "sync" system to basically disallow arbitrary loading and sharing of music and "just" dropping music onto it) being now considered an example of an open device.
Here's a talk about how the Voyager team fixed the flight data computer on Voyager 1 when a memory chip went bad on it a few years ago. It goes over how the flight computer works and he walks through a few assembly routines. https://www.youtube.com/watch?v=YcUycQoz0zg
Some of the challenges they had to deal with while developing the fix:
- The only source code they had for the flight data software was an OCR'd Microsoft Word document (with typos) that was likely scanned from a hard copy assembler listing printout.
- The processor runs a custom instruction set developed by JPL for the Voyager mission. The documentation they had on the processor was incomplete.
- Everybody who had designed the flight software was dead.
- They had no assembler, no debugger, and no processor simulator. They had no testbed, the only two FDS processors were in space.
The 2025 YouTube video is "How We Diagnosed and Fixed the 2023 Voyager 1 Anomaly from 15 Billion Miles Away" by David Cummings of JPL.
There is a Vimeo video of the Voyager team reacting when data first began trickling in from Voyager 1 after the fix in April 2024. "Voyager 1 Team Reacts to Receiving Engineering Data From Spacecraft" (JPLraw channel): https://vimeo.com/939376171
Cummings is the one against the back wall who shoots his two arms up in the air in celebration. He and Armen Arslanian (in the blue shirt to his left, right in the image) developed the software fix.
If anybody wants further context, here's an excellent paper on the status of the Voyager mission as of 2016, written by one of the engineers at JPL. It has an overview of what all the instruments on Voyager do and everything the team had done to keep the mission going as of that point. https://csclub.uwaterloo.ca/~pbarfuss/VIMChallenges.pdf I also highly recommend the documentary "It's Quieter in the Twilight" which is about the entire Voyager team and their efforts to keep the program operational.
For others, this truly excellent 2016 paper is "Voyager Interstellar Mission: Challenges of Flying a Very Old Spacecraft on a Very Long Mission" by Sun Kang Matsumoto. She was/is a Voyager Fault Protection and CCS Flight Software Systems Engineer (CCS was the onboard command computer) and she was also one of the "stars" in It's Quieter in the Twilight.
Assuming this is well done, it's an extremely cool product. The original Neo Geo systems and cartridges are ridiculously expensive on the used market and bootlegs are rampant. Even though they're charging $90/cartridge, that's still thousands of dollars less than what a lot of these games go for used.
The biggest concern I have is accuracy. SNK wouldn't be able to just start manufacturing their old chip designs from the 90s again because a lot of the chips in the Neo Geo from other companies are no longer made, such as the 68000, Z80, and YM2610. This means that they'd have to make a new SoC that incorporates the IP from those chips. At that point there's no real benefit to the ASIC over an FPGA. It means the system costs less to produce, but if they find any inaccuracies in their new SoC design they won't be able to release an update to fix them. I'm cautiously optimistic, but I'm not going to place a pre-order until they release more details about what exactly is going on under the hood.
Cloudflare has always operated this way. For example, they give DDoS protection to DDoS for hire services. This increases the supply of these services because it means they can't shut down their competitors by DDoSing each other, which in turn encourages more regular people to use Cloudflare so they won't get their sites DDoSed.
In the United States, not having a job for the short term means you lose your healthcare, for the medium term means you're living out of your car, and for the long term means you're out on the street, incarcerated, or dead. AI executives talk to the public like "investors are pouring billions into my new invention, the Job Killer 9000. Sure millions of people are going to get laid off and over time it'll force the price of wage work closer and closer to zero, but that's just the price of progress!" That in itself is inherently a violent threat. I am not surprised that some people are responding to it with violence.
reply