Times are tough out there, and many are starting to feel the pressure at the grocery store checkout line or the gas pump. But whenever you start to worry about affording life’s necessities, take comfort in the knowledge that somebody is so flush with cash that on Friday they decided to treat themselves and spend $3 million for a sealed copy of Super Mario Bros for the Nintendo Entertainment System.

Although we’re not going to say it necessarily justifies the insane price — a new record for the most ever paid for a video game, incidentally — Heritage Auctions does note in their press release that this is an exceptionally rare version of what’s admittedly one of the most iconic pieces of software ever produced. This is only one of three copies of this particular variant known to exist, which Nintendo apparently distributed to test markets in the United States ahead of the game’s official 1985 release.

In slightly more modern gaming news, Asha Sharma, the new head of Microsoft’s Xbox division, has been making some big swings to try and get Microsoft’s gaming division back on track after years of declining sales. As part of that effort, she recently penned an article detailing some of the challenges the company is facing, which includes some interesting hardware details.

According to the blog post, she claims that in February, the cost of memory and storage components for the Xbox console had doubled compared to the previous year. But those numbers have jumped again, and by the time the holidays roll around, she expects they’ll be paying five times what they did in 2024. That’s bad news for anyone looking to put an Xbox under the tree come Christmas, but even worse news as the company works on the console’s successor. Considering that today’s hardware from Sony and Microsoft can already set you back $700 USD depending on which version you get, it seems like we’re approaching a point where gaming consoles could price themselves out of the market.

Those thinking of mowing some lawns this summer to save up for their $1K next-generation consoles may be interested to hear that the Food and Drug Administration has put its stamp of approval on the first new sunscreen ingredient in the US in more than two decades. Bemotrizinol is a broad-spectrum UV absorber that knocks out 310 and 340 nm, and while Uncle Sam has taken his sweet time to give it the OK, the European Union has been slathering it on since 2000. The first company authorized to sell it in the US will be marketing it under the name Parsol Shield later this year, with other manufacturers set to follow in 2027.

While it seems the world has agreed on adding bemotrizinol to their sunscreens, many people are decidedly less enthusiastic about AI code in their open-source projects. One of those people is Drew DeVault, which is why he decided to fork Vim once he found out its maintainers were merging in code written by large language models (LLMs). Rather than break off at the last version untainted by clankers, Drew decided to divert from the upstream project at version 8.2.x. This means that some newer plugins may have compatibility issues, although security fixes and other selected updates from the 9.x branch have been back-ported to the newly coined Vim Classic. If you give it a shot, let us know in the comments.

Finally, if a non-AI fork of Vim is still too mainstream to scratch that itch for you, Phoronix is reporting that ReactOS can now run Half Life. If this were any other website, we might devote the next paragraph to explaining the significance of a nearly 30-year-old PC game being run on a free and open-source operating system designed to provide binary compatibility with Microsoft Windows. But it’s Sunday evening, and you’re reading Hackaday, so just take the win.

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.

The weather is warming up, and for many of us that means more time spent working out in the yard. You probably won’t find any new life or new civilizations out there, but if you’ve spent the last few months indoors on your computer, the garden may as well be a strange new world. In that case, you’d do well to equip the members of your landing party with this Star Trek: The Original Series hose sprayer designed by [Curt Turner].

If you’re wondering how [Curt] managed to 3D print a functional hose sprayer, the short answer is that he didn’t. Once assembled, the printed parts cleverly attach to the top of a standard sprayer, specifically the model 56516 “Pro Flo” from Orbit. Without the design constraints that would have come from trying to make the thing actually contain pressurized water, [Curt] was free to focus on the aesthetics, and it shows.

Even with a garden variety — no pun intended — sprayer strapped to the bottom, it’s remarkable how much the “Sprayser” looks like the real thing. Well, not real, but you know what we mean.

[Curt] has also done an excellent job documenting this project for others that want to imagine they’re fighting off Romulans in their backyard. He’s got assembly diagrams that break down which color each of the principle components is to be printed in, as well as a build video that we’ve embedded below.

We’ve seen a fair number of Star Trek props built over the years, some of which have packed in considerably more functionality than anything they would have had back on the set. These days you can even by an officially licensed tricorder that can actually do some of the things the fictional versions were capable of.

When the Artemis lunar program was first conceived, the third mission would have seen astronauts step foot on the Moon for the first time since Apollo 17 in 1972. But as hard as getting into space is, a sojourn to our nearest celestial neighbor is even more mindbogglingly complex, and so earlier this year it was announced that actually landing on the Moon would be pushed out to the fourth mission.

In turn Artemis III would take a page out of the Apollo 9 playbook and test out rendezvous and docking procedures with commercial landers while operating in the relative safety of low Earth orbit. Moving the target date for the landing a few years down the road gave all involved parties a little more breathing room, but it also provided a valuable opportunity to gain insight into the performance of the vehicles and systems ahead of the critical moment. In the original timeline, the first time Orion would attempt to dock with the lander would have been just before descending to the lunar surface — leaving precious little time to troubleshoot should anything go wrong.

Yesterday NASA held a press conference to update the public on their progress towards the planned 2027 launch of Artemis III, which included the long-awaited announcement of the crew that will kick the tires on the next-generation lunar landers being developed by SpaceX and Blue Origin

Meet the Artemis III Crew

One Mission, Three Launches

Although astronauts are by their nature the best of the best, the collected experience and knowledge of the Artemis III crew is truly incredible — and for good reason. This flight will be one of the most challenging and technically complex operations ever conducted in space, perhaps second only to the Apollo Moon landings themselves. In the most ambitious version of the plan, three spacecraft launched by three different booster rockets will conduct a carefully choreographed operation over the course of two weeks.

To start the first phase of Artemis III, Blue Origin will use one of their New Glenn rockets to carry the Blue Moon MK2 lander into low Earth orbit. The lander is designed to spend up to 90 days in space, which will give NASA a comfortable window of opportunity to get their Space Launch System rocket and Orion spacecraft ready for liftoff. After launch Orion will rendezvous and dock with the lander, and the crew will spend the next two days performing various tests and demonstrations. If everything goes well, they will ultimately enter the lander itself and don prototypes of the spacesuits that Axiom Space is developing for the Artemis IV crew to wear on the lunar surface.

Meanwhile, SpaceX will be preparing a modified version of their Starship V3 spacecraft for liftoff atop the Super Heavy booster. Once the Orion spacecraft is undocked and clear of the Blue Moon MK2, the prototype Starship Human Landing System (HLS) will launch and meet the capsule in orbit. According to SpaceX representatives, the vehicle itself won’t be too far removed from the version that completed a test flight back in May. Compared to Blue Origin’s lander, which will feature a boilerplate cabin design and functional life support systems, the Artemis III crew won’t be able to enter this early version of HLS.

Likely in expectation that comparisons would be made between the apparent capabilities of the two landers, SpaceX Vice President of Space Operations Jessica Jensen pointed out that many of the systems that will be used in Starship HLS such as the life support and avionics are derived from the flight-proven hardware used on the Crew Dragon — with some components such as the docking system being effectively identical. From the perspective of SpaceX, it’s more important to focus on testing the new hardware and procedures being developed specifically for the Moon.

Given that astronauts will not be able to enter the Starship HLS prototype, it’s expected the crew will spend significantly less time docked to it. After conducting some maneuvers to see how the two vehicles handle in relation to each other, the Orion will depart orbit and head for a splashdown in the Pacific.

Setting Course For Artemis IV

Although the press conference was about the upcoming mission, Jensen did give some brief details on how SpaceX and NASA are working together to refine the procedures for Artemis IV in 2028.

Back when Artemis III was set to touch down on the lunar surface, the plan was for Starship HLS to first enter into a relatively uncommon Near-Rectilinear Halo Orbit (NRHO) around the Moon, where it would eventually be met by the Orion capsule. However this was largely predicated on the idea that the Lunar Gateway Station would also be in NRHO. Now that the construction of Gateway has been abandoned, there’s no reason to rendezvous in that particular orbit.

Instead Orion will now dock with Starship HLS in low Earth orbit, just like it will on Artemis III. From there, Starship will use its own engines to perform the critical trans-lunar injection burn and put both craft on course towards the Moon.

This approach is not only easier to execute, but will require less propellant and therefore fewer refueling flights — directly addressing a common criticism leveled against the Artemis architecture.

High Risk, High Reward

Calling Artemis III ambitious would be an understatement. A mission involving a trio of spacecraft and their respective launch vehicles, two of which being early prototypes, has never been attempted in the history of spaceflight. Getting just one vehicle off the ground is a challenge in itself, and although experienced gained over the decades thanks to the International Space Station has made the subsequent rendezvous between two craft relatively routine, doing it twice during the same mission adds a whole new dimension.

Even the most ardent space fan has to admit it’s exceptionally difficult to believe that the involved parties can put such a bold plan into action in the next ~18 months, especially given the recent New Glenn explosion that has left Blue Origin’s launchpad in shambles. But it will certainly be exciting to see them try.

Even if you’re not normally interested in what’s happening in low Earth orbit, you probably heard that last week NASA ordered its personnel aboard the International Space Station to button themselves up in the docked Dragon spacecraft and await further instructions should they need to make a hasty departure. Known as Safe Haven, this emergency procedure is performed whenever there’s an elevated risk of damage to the Station.

NASA has provided an update on what happened, but it arguably leaves more questions than answers. Usually, crews go to their Safe Haven because some bit of space junk has wandered to close to the orbiting complex, but this time it was because Russian cosmonauts Sergey Kud-Sverchkov and Sergei Mikayev were getting ready to start cutting into the walls of the PrK transfer tunnel in an effort to address its persistent air leak.

After about an hour and a half, the Russians called off the effort and NASA gave their people the OK to leave the Dragon and return to their normal duties. NASA Press Secretary Bethany Stevens later posted on social media that the space agency would “look forward to working with Roscosmos on a collaborative approach to address the leaks” in the future. There’s currently no word on what a future repair attempt may entail, or when it would be attempted.

This is one of those things were we might not hear the full story for some time, but it sure does sound like not only did the Russians want to do something that NASA didn’t think was safe, but that the whole thing was sprung on them at the last moment. To give you an idea of how serious Mission Control was taking the situation, they decided to cram five people into a Dragon capsule that only has four seats — it certainly would have made for one wild ride down to Earth if they were given the order to evacuate.

What do you want to bet there were some frantic international calls taking place while the astronauts were hiding out in their designated lifeboat?

Christopher Nolan’s The Odyssey isn’t hitting theaters for another month or so, but if you’re already planning your trip to the cineplex, you may want to check out this page on the movie’s website which lets you view the trailer in the six (!) different formats it’s being released in.

We don’t really have an opinion on the big-screen adaptation of the epic tale as a piece of media, but from a technical standpoint, it’s interesting to see how the viewing experience changes between the 70mm IMAX version with an aspect ratio of 1.43:1 and the 35mm cut at 2.39:1. Unfortunately, the website offers no way to approximate what the movie will look like once compressed, streamed over the Internet, and displayed on a cheap TCL TV, to say nothing of how the viewing experience will be impacted should you watch the movie on your phone by way of a series of short YouTube clips while going to the bathroom. Maybe Nolan is saving that for his next film.

If you head over to the movies in one of Waymo’s vehicles, you can feel a little better about the long-term ecological impact of your trip thanks to a recently announced partnership between the autonomous car maker and B2U Storage Solutions. Under the agreement, old batteries pulled from Waymo’s fleet of self-driving electric cars will get a second life as localized grid storage.

The idea is that batteries which no longer hold enough charge to power a robo-taxi should still have enough capacity to store the energy produced by renewable sources so it can be doled out later when the demand goes up. By installing these batteries in the cities that Waymo actually operates their vehicles in, they don’t have to worry about shipping them around either — they can just yank them out of the car, and wire them right into the grid. Of course, eventually the batteries will be too cooked to adequately perform in this role as well, but this should give them a few more productive years before they get torn down and scrapped.

Speaking of scrapping, the Ladybird project has announced a pretty radical change for an open source project: as of Friday no public pull requests to the codebase will be accepted, and the only people who can make changes to the code will be the official maintainers. The license for the project isn’t changing, so folks are still free to create forks and modify the code of the scratch-built browser however they wish, but they’ll have to do so with the understanding that their changes will likely never get merged back upstream.

So why the change? You probably guessed it already: they are sick of people sending in patches developed with AI. We’ve talked about this issue previously, and the Ladybird devs are hardly the only ones struggling to separate the wheat from the vibecoded chaff. For what it’s worth, the announcement makes it clear that the team isn’t necessarily against the responsible use of AI in software development. Their concern stems more from the fact that AI lets anybody and everybody produce code that at least looks valid, and it makes it harder to figure out what’s good and worthy of inclusion and what should probably stay in somebody’s personal repo.

On the subject of software development, health-conscious free software aficionados will be excited to hear that the GNUtrition project hit version 0.33 on Friday. For those keeping track, the free-as-in-speech tool for *nix nerds looking to keep track of their caloric intake hasn’t seen a major release since 2012. The update takes into account the latest US Department of Agriculture (USDA) dietary data, and somewhat surprisingly, switches the whole codebase from Python 2 to pure C. Patches which would have allowed the new build of GNUtrition to calculate the nutritional value of substances eaten off of one’s shoe were mysteriously vetoed from the highest levels of the Free Software Foundation.

One more software link for the road: assuming it hasn’t been taken down by Nintendo’s rabid lawyers by the time this hits the front page, check out this WebASM port of Pokemon Emerald that you can play right in the browser.

The game came out more than 20 years ago for the Game Boy Advance, so the fact that it can run in a modern browser isn’t exactly shocking given how much of today’s software lives on the web. But we still love seeing these decompilation efforts and all the hacks that are made possible once you’ve got the code to work from rather than having to emulate the original system.

Finally, the good folks at iFixit have released a video wherein they take apart fake Apple products that were purchased in the electronics wonderland of Shenzhen. As you might expect, the gadgets they picked up all look fairly convincing at arm’s length, but many of their features don’t actually work and their internals are cobbled together with random ill-fitting bits and bobs.

At the end of the video they do note that the knock-offs are in general easier to take apart than their Cupertino counterparts, but that this doesn’t really help with their repairability or long-term viability as you’ll likely have a hell of a time tracking down replacement parts for the Number 1 Best AirPoods Max.

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.

If you’ve ever worked with I2C, you know its one of those things that makes working with modern microcontrollers such a pleasure. With a few wires and not many more lines of code, you can communicate with all sorts of hardware such as sensors, displays, and input devices. There are even I2C keyboards out there, although they tend to be a bit pokey — and not in the good way as it pertains to keyboards.

But the bt2i2c project from [Roberto Alsina] promises to improve things. With his firmware flashed to a Pi Pico W, you can establish a connection with any standard Bluetooth keyboard and have the keystrokes sent over the wire via I2C. As far as your project is concerned, the input will appear to be coming from a BlackBerry BBQ20/BBQ10 keyboard using the address 0x1F, which means that there’s already plenty of code out there to work with. While [Roberto] explains its not strictly necessary, connecting a ST7789 display to the Pi Pico over SPI will give you some visual feedback on connection status.

As microcontrollers become increasingly powerful and capable of the sort of thing we would once have done on a “real” computer, a project like this has some fascinating potential. We’ve seen a number of “writerdeck” projects running on chips like the ESP32, and it’s not hard to see the appeal of being able to easily pair your favorite Bluetooth keyboard up to one of them.

These days, we take it for granted that a video game console will have multiple USB ports. There’s even an expectation that basic peripherals such as storage devices will “Just Work” when plugged into the system — a far cry from the days when each system had its own proprietary memory card.

The original Xbox from 2001 actually had USB ports as well, it’s just that they were used for the controllers and had non-standard connectors that kept you from plugging in other devices. But a simple adapter gets you a standard USB-A port, and after that it’s just a matter of software. Like this homebrew project to get generic USB webcams working on Microsoft’s first foray into console gaming.

Well, “generic” may be pushing it a bit, as the project by [Darkone83] currently lists only two compatible cameras. The first is the Xbox Live Vision Camera, which was never intended to be used on the original Xbox and was instead an accessory for Microsoft’s follow-up console, the Xbox 360. Interestingly, the other supported camera happens to be Sony’s PS2 EyeToy. Claiming that you plugged a PS2 camera into your Xbox would have been fighting words back on the playground circa 2003, but now it’s a reality thanks to the power of open source.

Now there technically was a camera for the original Xbox, but it was only released in Japan and is quite rare. Perhaps unsurprisingly it used the same OV519 chipset as the EyeToy and later Vision Camera, and reverse engineering how the console communicated with it was critical to the development of this project.

As of right now, there’s not much practical application for this webcam driver. It just shows the image from the camera on your TV in glorious 320×240 resolution. But now that the code to make it work is out in the wild, hopefully other Xbox homebrew projects will add support for it.

Although things aren’t quite as active these days as they once were, the hacking scene for the original Xbox is the stuff of legend. If you ever see one of this gargantuan consoles at a flea market for cheap, there’s still plenty of fun to be had pushing the system outside of its comfort zone.