Disappointing news this week for those longing for same-hour Amazon delivery as the retail giant tapped the brakes on its Prime Air drone deliveries. The pause is partially blamed on a December incident at the company’s Pendleton, Oregon test facility, where two MK30 delivery drones collided in midair during light rain conditions. A Bloomberg report states that the crash, which resulted in one of the drones catching fire on the ground, was due to a software error related to the weather. As a result, they decided to ground their entire fleet, which provides 60-minute delivery to test markets in Arizona and Texas, until a software update can be issued.
Hackaday Columns4258 Articles
This excellent content from the Hackaday writing crew highlights recurring topics and popular series like Linux-Fu, 3D-Printering, Hackaday Links, This Week in Security, Inputs of Interest, Profiles in Science, Retrotechtacular, Ask Hackaday, Teardowns, Reviews, and many more.
Networking History Lessons
Do they teach networking history classes yet? Or is it still too soon?
I was reading [Al]’s first installment of the Forgotten Internet series, on UUCP. The short summary is that it was a system for sending files across computers that were connected, intermittently, by point-to-point phone lines. Each computer knew the phone numbers of a few others, but none of them had anything like a global routing map, and IP addresses were still in the future. Still, it enabled file transfer and even limited remote access across the globe. And while some files contained computer programs, others files contained more human messages, which makes UUCP also a precursor to e-mail.
What struck me is how intuitively many of this system’s natural conditions and limitations lead to the way we network today. From phone numbers came the need for IP addresses. And from the annoyance of having know how the computers were connected, and to use the bang notation to route a message from one computer to another through intermediaries, would come our modern routing protocols, simply because computer nerds like to automate hassles wherever possible.
But back to networking history. I guess I learned my networking on the mean streets, by running my own Linux system, and web servers, and mail servers. I knew enough networking to get by, but that mostly focused on the current-day application, and my beard is not quite grey enough to have been around for the UUCP era. So I’m only realizing now that knowing how the system evolved over time helps a lot in understanding why it is the way it is, and thus how it functions. I had a bit of a “eureka” moment reading about UUCP.
In physics or any other science, you learn not just the status quo in the field, but also how it developed over the centuries. It’s important to know something about the theory of the aether to know what special relativity was up against, for instance, or the various historical models of the atom, to see how they inform modern chemistry and physics. But these are old sciences with a lot of obsolete theories. Is computer science old enough that they teach networking history? They should!
Hackaday Podcast Episode 305: Caustic Clocks, Practice Bones, And Brick Layers
This week, Hackaday’s Elliot Williams and Kristina Panos joined forces and Wonder-Twin rings to bring you the latest news, mystery sound, and of course, a big bunch of hacks from the previous week.
First up in the news: Big boo to Bambu Labs, who have tried to clarify their new authentication scheme and probably only dug themselves in deeper with their customers.
On What’s That Sound, Kristina didn’t get close at all, but at least had a guess this time. Do know what it is? Let us know, and if you’re right and your number comes up, you can keep warm in a limited edition Hackaday Podcast t-shirt.
Then it’s on to the hacks and such beginning with a rather nice reverse-engineering of the Yamaha PRS-E433 keyboard, which led to a slice of Bad Apple playing on the tiny screen.
After that, we take a look at an NES musical instrument, how to make wires explode with energy, and a really cool space mouse that uses flexures. Finally, we talk about a piece of forgotten Internet history, and a whole bunch of keyboards.
Check out the links below if you want to follow along, and as always, tell us what you think about this episode in the comments!
Download in DRM-free MP3 and savor at your leisure.
Continue reading “Hackaday Podcast Episode 305: Caustic Clocks, Practice Bones, And Brick Layers”
This Week In Security: ClamAV, The AMD Leak, And The Unencrypted Power Grid
Cisco’s ClamAV has a heap-based buffer overflow in its OLE2 file scanning. That’s a big deal, because ClamAV is used to scan file attachments on incoming emails. All it takes to trigger the vulnerability is to send a malicious file through an email system that uses ClamAV.
The exact vulnerability is a string termination check that can fail to trigger, leading to a buffer over-read. That’s a lot better than a buffer overflow while writing to memory. That detail is why this vulnerability is strictly a Denial of Service problem. The memory read results in process termination, presumably a segfault for reading protected memory. There are Proof of Concepts (PoCs) available, but so far no reports of the vulnerability being used in the wild.
Continue reading “This Week In Security: ClamAV, The AMD Leak, And The Unencrypted Power Grid”
FLOSS Weekly Episode 817: Incompatible With Reality
This week, Jonathan Bennett and Dan Lynch chat with Stefano Zacchiroli about Debian and Software Heritage!
Continue reading “FLOSS Weekly Episode 817: Incompatible With Reality”
Keebin’ With Kristina: The One With The Hardware-Layered Keyboard
You know (or maybe you didn’t), I get super excited when y’all use the links at the bottom of this round-up we call Keebin’ to communicate with your old pal Kristina about your various labors of love. So just remember that.
Case in point: I was typing up this very issue when I heard from [Jay Crutti] and [Marcel Erz]. Both are out there making replacement keyboards for TRS-80s — [Jay] for Models 3 and 4, and [Marcel] for the Model 1. Oooh, I said to myself. This is going at the top.
Relevant tangent time: I remember in the 90s having a pile of computers in my parents’ basement of various vintages, a TRS-80 Model 2 among them. (Did I ever tell you about the time I got pulled over for speeding with a bunch of different computers in the backseat? I was like no, officer, first of all, those are old machines that no one would really want, and I swear I didn’t steal them.)
I think the TRS-80 is probably the one I miss the most. If I still had it, you can bet I would be using [Jay] and [Marcel]’s work to build my own replacement keyboard, which the 40-year-old machine would likely need at this point if the Model 4 is any indication with its failing keyboard contacts.
To create the replacements, [Jay] used Keyboard Layout Editor (KLE), Plate & Case Builder, and EasyEDA. Using the schematic from the maintenance manual, he matched the row/column wiring of the original matrix with Cherry MX footprints. Be sure to check out [Jay]’s site for a link to the project files, or to purchase parts or an assembled keyboard. On the hunt for TRS-80 parts in general? Look no further than [Marcel]’s site.
Continue reading “Keebin’ With Kristina: The One With The Hardware-Layered Keyboard”
Hackaday Links: January 19, 2025
This week, we witnessed a couple of space oopsies as both Starship and New Glenn suffered in-flight mishaps on the same day. SpaceX’s Starship was the more spectacular, with the upper stage of the seventh test flight of the full stack experiencing a “rapid unscheduled disassembly” thanks to a fire developing in the aft section of the stage somewhere over the Turks and Caicos islands, about eight and a half minutes after takeoff from Boca Chica. The good news is that the RUD happened after first-stage separation, and that the Super Heavy booster was not only able to safely return to the pad but also made another successful “chopsticks” landing on the tower. Sorry, that’s just never going to get old.
On the Bezos side of the billionaire rocket club, the maiden flight of Blue Origin’s New Glenn ended with the opposite problem. The upper stage reached orbit, but the reusable booster didn’t make it back to the landing barge parked off the Bahamas. What exactly happened isn’t clear yet, but judging by the telemetry the booster was coming in mighty fast, which may indicate that the engines didn’t restart fully and the thing just broke up when it got into the denser part of the atmosphere.