Your Console, Your Cartridge, You Choose? Nintendo Faces A Challenge

If you read our articles, you’ll notice that we will usually feature images related to the subjects we talk about. If they came from another source and they’re not CC-licensed or similar then they are the property of someone else but we are using them under a doctrine known as fair use. Excerpts of copyrighted material may be used under fair use for the purposes of such things as journalistic reporting, so for example we can use a copyrighted picture of Captain America were we to write about Marvel superheroes. Some content owners still try to stop this, and it’s one of them that [Linus Tech Tips] has in their sights as they have published a guide to running Nintendo Switch games on a Steam Deck without they believe giving any justifiable cause for the notoriously litigious game giant to take action. It’s full of carefully blurred Nintendo IP, and there is no coverage of pirate software downloads.

On one hand it’s about a heavy-handed console developer taking down small online content producers, but there’s another angle which is far more relevant to the hardware community who read Hackaday. It also has application in the field of software emulation, because while the console manufacturer would prefer to stop all but their own unmodified hardware running a game there should be nothing to stop a legally owned piece of software or hardware being run in any way its owner chooses. This is the central thesis explored at the end of the video, and the gimmick of trying to draw Nintendo into the open on the matter is their way of bringing publicity to it.

Even though [Linus Tech Tips] is probably one of the most viewed technology YouTube channels, it’s clear that Nintendo will have the deeper pockets should they choose to rise to the bait. So we’re sure their lawyers are all over this as we write, but we’d be interested to see whether the claims made in the video are enough to see it stay up. It would be nice to think that it might cause Nintendo to reconsider some of their policies, but we’re not holding our breath. Continue reading “Your Console, Your Cartridge, You Choose? Nintendo Faces A Challenge”

Hackaday Links Column Banner

Hackaday Links: March 27, 2022

Remember that time back in 2021 when a huge container ship blocked the Suez Canal and disrupted world shipping for a week? Well, something a little like that is playing out again, this time in the Chesapeake Bay outside of the Port of Baltimore, where the MV Ever Forward ran aground over a week ago as it was headed out to sea. Luckily, the mammoth container ship isn’t in quite as narrow a space as her canal-occluding sister ship Ever Given was last year, so traffic isn’t nearly as impacted. But the recovery operation is causing a stir, and refloating a ship that was drawing 13 meters when it strayed from the shipping channel into a muddy-bottomed area that’s only about 6 meters deep is going to be quite a feat of marine engineering. Merchant Marine YouTuber Chief MAKOi has a good rundown of what’s going on, and what will be required to get the ship moving again.

With the pace of deep-space exploration increasing dramatically of late, and with a full slate of missions planned for the future, it was good news to hear that NASA added another antenna to its Deep Space Network. The huge dish antenna, dubbed DSS-53, is the fourteenth dish in the DSN network, which spans three sites: Goldstone in California; outside of Canberra in Australia; and in Madrid, where the new dish was installed. The 34-meter dish will add 8% more capacity to the network; that may not sound like much, but with the DSN currently supporting 40 missions and with close to that number of missions planned, every little bit counts. We find the DSN fascinating, enough so that we did an article on the system a few years ago. We also love the insider’s scoop on DSN operations that @Richard Stephenson, one of the Canberra operators, provides.

Does anybody know what’s up with Benchy? We got a tip the other day that the trusty benchmarking tugboat model has gone missing from several sites. It sure looks like Sketchfab and Thingiverse have deleted their Benchy files, while other sites still seem to allow access. We poked around a bit but couldn’t get a clear picture of what’s going on, if anything. If anyone has information, let us know in the comments. We sure hope this isn’t some kind of intellectual property thing, where you’re going to have to cough up money to print a Benchy.

Speaking of IP protections, if you’ve ever wondered how far a company will go to enforce its position, look no further than Andrew Zonenberg’s “teardown” of an anti-counterfeiting label that Hewlett Packard uses on their ink cartridges. There’s a dizzying array of technologies embedded inside what appears to be a simple label. In addition to the standard stuff, like the little cuts that make it difficult to peel a tag off one item and place it on another — commonly used to thwart “price swapping” retail thefts — there’s an almost holographic area of the label. Zooming in with a microscope, the color-shifting image appears to be made from tiny hexagonal cells that almost look like the pixels in an e-ink display. Zooming in even further, the pixels offer an even bigger (smaller) surprise. Take a look, and marvel at the effort involved in making sure you pay top dollar for printer ink.

And finally, we got a tip a couple of weeks ago on a video about jerry cans. If that sounds boring, stop reading right now — this one won’t reach you. But if you’re even marginally interested in engineering design and military history, make sure you watch this video. What is now known to the US military as “Can, Gasoline, Military 5-Gallon (S/S by MIL-C-53109)” and colloquially known as the NATO jerry can, started life as the Wehrmacht-Einheitskanister, a 20-liter jug whose design addresses a long list of specifications, from the amount of liquid it could contain to how the cans would be carried. The original could serve as a master class in good design, and some of the jugs that were built in the 1940s are still in service and actively sought by collectors of militaria. Cheap knockoffs are out there, of course, but after watching this video, we’ve developed a taste for jerry cans that only the original will sate.

Control Your Web Browser Like It’s 1969

Imagine for a moment that you’ve been tasked with developing a device for interfacing with a global network of interconnected devices. Would you purposely design a spring-loaded dial that can do nothing but switch a single set of contacts on and off from 1 to 10 times? What kind of crazy world would we have to live in where something like that was the pinnacle of technology?

Obviously, such a world once existed, and now that we’ve rolled the calendar ahead a half-century or so, both our networks and our interfaces have gotten more complex, if arguably better. But [Jan Derogee] thinks a step backward is on order, and so he built this rotary phone web browser. The idea is simple: pick up the handset and dial the IP address of the server you want to connect to. DNS? Bah, who needs it?

Of course there is the teensy issue that most websites can’t be directly accessed via IP address anymore, but fear not – [Jan] has an incredibly obfuscated solution to that. It relies on the fact that many numbers sound like common phrases when sounded out in Chinese, so there end up being a lot of websites that have number-based URLs. He provides an example using the number 517, which sounds a bit like “I want to eat,” to access the Chinese website of McDonald’s. How the number seven sounding like both “eat” and “wife” is resolved is left as an exercise to the reader.

And here we thought [Jan]’s rotary number pad was of questionable value. Still, we appreciate this build, and putting old phones back into service in any capacity is always appreciated.

Continue reading “Control Your Web Browser Like It’s 1969”

Bidirectional IP With New Packet Radio

There are a few options if you want to network computers on amateur radio. There are WiFi hacks of sort, and of course there’s always packet radio. New Packet Radio, a project from [f4hdk] that’s now on hackaday.io, is unlike anything we’ve seen before. It’s a modem that’s ready to go, uses standard 433 ISM band chips, should only cost $80 to build, and it supports bidirectional IP traffic.

The introductory documentation for this project (PDF) lays out the use case, protocol, and hardware for NPR. It’s based on chips designed for the 433MHz ISM band, specifically the SI4463 ISM band radio from Silicon Labs. Off the shelf amplifiers are used, and the rest of the modem consists of an Mbed Nucleo and a Wiznet W5500 Ethernet module. There is one single modem type for masters and clients. The network is designed so that a master serves as a bridge between Hamnet, a high-speed mesh network that can connect to the wider Internet. This master connects to up to seven clients simultaneously. Alternatively, there is a point-to-point configuration that allows two clients to connect to each other at about 200 kbps.

Being a 434 MHz device, this just isn’t going to fly in the US, but the relevant chip will work with the 915 MHz ISM band. This is a great solution to IP over radio, and like a number of popular amateur radio projects, it started with the hardware hackers first.

Want To Learn Ethernet? Write Your Own Darn AVR Bootloader!

There’s a school of thought that says that to fully understand something, you need to build it yourself. OK, we’re not sure it’s really a school of thought, but that describes a heck of a lot of projects around these parts.

[Tim] aka [mitxela] wrote kiloboot partly because he wanted an Ethernet-capable Trivial File Transfer Protocol (TFTP) bootloader for an ATMega-powered project, and partly because he wanted to understand the Internet. See, if you’re writing a bootloader, you’ve got a limited amount of space and no device drivers or libraries of any kind to fall back on, so you’re going to learn your topic of choice the hard way.

[Tim]’s writeup of the odyssey of cramming so much into 1,000 bytes of code is fantastic. While explaining the Internet takes significantly more space than the Ethernet-capable bootloader itself, we’d wager that you’ll enjoy the compressed overview of UDP, IP, TFTP, and AVR bootloader wizardry as much as we did. And yes, at the end of the day, you’ve also got an Internet-flashable Arduino, which is just what the doctor ordered if you’re building a simple wired IoT device and you get tired of running down to the basement to upload new firmware.

Oh, and in case you hadn’t noticed, cramming an Ethernet bootloader into 1 kB is amazing.

Speaking of bootloaders, if you’re building an I2C slave device out of an ATtiny85¸ you’ll want to check out this bootloader that runs on the tiny chip.

Becoming Your Own ISP, Just For Fun

When moving into a new house, it’s important to arrange for the connection of basic utilities. Electricity, water, and gas are simple enough, and then it’s generally fairly easy to set up a connection to an ISP for your internet connection. A router plugs into a phone line, or maybe a fiber connection and lovely packets start flowing out of the wall. But if you’re connected to the internet through an ISP, how is the ISP connected? [Kenneth] answers this in the form of an amusing tale.

It was during the purchase of data centre rack space that [Kenneth]’s challenge was laid down by a friend. Rather then simply rely on the connection provided by the data centre, they would instead rely on forging their own connection to the ‘net, essentially becoming their own Internet Service Provider.

This is known as creating an Autonomous System. To do this involves several challenges, the first of which is understanding just how things work at this level of networking. [Kenneth] explains the vagaries of the Border Gateway Protocol, and why its neccessary to secure your own address space. There’s also an amusing discussion on the routing hardware required for such a feat and why [Kenneth]’s setup may fall over within the next two years or so.

It’s not for the faint hearted, and takes a fair bit of paperwork, but [Kenneth] has provided an excellent guide to the process if you really, really just need to own your own corner of the internet. That said, there are other networking tricks to cut your teeth on if you’d like a simpler challenge, like tunneling IP over ICMP.

 

Trademarking Makerspace (Again)

A British company has filed a trademark application for the word ‘MakerSpace’. While we’ve seen companies attempt to latch on to popular Maker phrases before, Gratnells Limited, the company in question, is a manufacturer of plastic containers, carts, and other various storage solutions. These products apparently provide a space to store all the stuff you make. Something along those lines.

This isn’t the first time we’ve seen someone try to glom onto the immense amount of marketing Make: has put into the term ‘makerspace’. In 2015, UnternehmerTUM MakerSpaceGmbH, an obviously German tech accelerator based in Munich, filed an application to trademark the word ‘Makerspace’. A few days later, we got word this makerspace wasn’t trying to enforce anything, they were just trying to keep the rug from being pulled out from under them. It was a defensive trademark, if something like that could ever exist (and it can’t under US trademark law). Swift and efficient German bureaucracy prevailed, and the trademark was rejected.

The trademark in question here covers goods including, ‘metal hardware and building materials’, ‘trolleys, trolleys with trays’, ‘guide rails of non-metallic materials’, and ‘lids for containers’, among other storage-related items. While this is far outside the usual meaning for a ‘makerspace’ – a building or club with a whole bunch of tools – if this trademark is approved, there is always the possibility of overzealous solicitors.

Fortunately, Gratnells released a statement today saying they would not defend or continue this trademark. This is in light of the recent, limited reaction to the trademark application. The word Makerspace is safe again another day.

Thanks [Tom] for the tip.