Last year marked the 30th anniversary of the Internet Relay Chat protocol (IRC) and it is hard to imagine that [Jarkko Oikarinen] could have foreseen the impact his invention would one day have on the world as we know it. How it would turn from a simple, decentralized real-time communication system for university-internal use into a global phenomenon, connecting millions of users all over the world, forming its own subculture, eventually reaching mainstream status in some parts of the world — including a Eurodance song about a bot topping European music charts.
Those days of glory, however, have long been gone, and with it the version of an internet where IRC was the ideal choice. What was once a refuge to escape the real world has since become the fundamental centerpiece of that same real world, and our ways of communicating with each other has moved on with it. Nevertheless, despite a shift in mainstream and everyday communication behavior, IRC is still relevant enough today, and going especially strong in the open source community, with freenode, as one of the oldest networks, being the most frequently used one, along some smaller ones like OFTC and Mozilla’s own dedicated network. But that is about to change.
Last month, Mozilla’s envoy [Mike Hoye] announced the decommissioning of irc.mozilla.org within “the next small number of months“, and moving all communication to a new, or at least different system. And while this only affects Mozilla’s own, standalone IRC network and projects, and not the entire open source community, it is a rather substantial move, considering Mozilla’s overall reach and impact on the internet itself — past, present, and now even more the future. Let’s face it, IRC has been dying for years, but there is also no genuine alternative available yet that could truly replace it. With Mozilla as driving force, there is an actual chance that they will come up with a worthy replacement that transforms IRC’s spirit into the modern era.
When I went to a hacker camp in the Netherlands in February I was expecting to spend a few days in a comfortable venue with a bunch of friends, drink some beer, see a chiptune gig, and say “Ooh!” a lot at the exciting projects people brought along. I did all of those things, but I also opened the door to something unexpected. The folks from RevSpace in the Hague brought along their portable forge, and before long I found myself working a piece of hot rebar while wearing comically unsuitable clothing. One thing led to another, and I received an invite to come along and see another metalworking project of theirs: to go form ore to ornamental technology all in one weekend.
From Dirt To Space is a collaboration between Dutch hackerspaces with a simple aim: to take iron ore and process it into a component that will be launched into space. The full project is to be attempted at the German CCCamp hacker camp in August, but to test the equipment and techniques a trial run was required. Thus I found myself in a Le Shuttle car transporter train in the Channel Tunnel, headed for the Hack42 hackerspace in Arnhem where all the parties involved would convene.
Computer games have been around about as long as computers have. And though it may be hard to believe, Zork, a text-based adventure game, was the Fortnite of its time. But Zork is more than that. For portability and size reasons, Zork itself is written in Zork Implementation Language (ZIL), makes heavy use of the brand-new concept of object-oriented programming, and runs on a virtual machine. All this back in 1979. They used every trick in the book to pack as much of the Underground Empire into computers that had only 32 kB of RAM. But more even more than a technological tour de force, Zork is an unmissable milestone in the history of computer gaming. But it didn’t spring up out of nowhere.
The computer revolution had just taken a fierce hold during the second World War, and showed no sign of subsiding during the 1950s and 1960s. More affordable computer systems were becoming available for purchase by businesses as well as universities. MIT’s Laboratory for Computer Science (LCS) was fortunate to have ties to ARPA, which gave MIT’s LCS and AI labs (formerly part of Project MAC) access to considerable computing resources, mostly in the form of DEC PDP systems.
The result: students at the MIT Dynamic Modeling Group (part of LCS) having access to a PDP-10 KA10 mainframe — heavy iron at the time. Though this PDP-10 was the original 1968 model with discrete transistor Flip Chip modules and wire-wrapping, it had been heavily modified, adding virtual memory and paging support to expand the original 1,152 kB of core memory. Running the MIT-developed Incompatible Timesharing System (ITS) OS, it was a highly capable multi-user system.
We were all glued to our screens for a moment a few weeks ago, watching the Scaled Composites Stratolaunch dual-fuselage space launch platform aircraft make its first flight. The six-engined aircraft represents an impressive technical feat by any standard, and with a wingspan of 385 ft (117 m) and payload weight of 550,000 lb (250 t), is touted as the largest ever flown.
Our own Brian Benchoff took a look at the possibility of hauling more mundane cargo as an alternative (and possibly more popular) use of its lifting capabilities. And in doing so mentioned that “by most measure that matter” this is the largest aircraft ever built. There are several contenders for the title of largest aircraft that depend upon different statistics, so which one really is the largest? Sometimes it’s not as clear as you’d think, but finding out leads us into a fascinating review of some unusual aeronautical engineering.
When it comes to SpaceX, or perhaps more accurately its somewhat eccentric founder and CEO Elon Musk, it can be difficult to separate fact from fiction. For as many incredible successes SpaceX has had, there’s an equal number of projects or ideas which get quietly delayed or shelved entirely once it becomes clear the technical challenges are greater than anticipated. There’s also Elon’s particular brand of humor to contend with; most people assumed his claim that the first Falcon Heavy payload would be his own personal Tesla Roadster was a joke until he Tweeted the first shots of it being installed inside the rocket’s fairing.
So a few years ago when Elon first mentioned Starlink, SpaceX’s plan for providing worldwide high-speed Internet access via a mega-constellation of as many as 12,000 individual satellites, it’s no surprise that many met the claims with a healthy dose of skepticism. The profitability of Starlink was intrinsically linked to SpaceX’s ability to substantially lower the cost of getting to orbit through reusable launch vehicles, a capability the company had yet to successfully demonstrate. It seemed like a classic cart before the horse scenario.
But today, not only has SpaceX begun regularly reusing the latest version of their Falcon 9 rocket, but Starlink satellites will soon be in orbit around the Earth. They’re early prototypes that aren’t as capable as the final production versions, and with only 60 of them on the first launch it’s still a far cry from thousands of satellites which would be required for the system to reach operational status, but there’s no question they’re real.
During a media call on May 15th, Elon Musk let slip more technical information about the Starlink satellites than we’ve ever had before, giving us the first solid details on the satellites themselves, what the company’s goals are, and even a rough idea when the network might become operational.
It was foolish to think that the adventure of the Mario Bros. would ever exist outside of the castle walls of the Nintendo Entertainment System. Except for that one time it did. The Hudson Soft company was a close collaborator with Nintendo, and parlayed that favor into being tasked with bringing Super Mario Bros. to platforms beyond the NES. The result of that collaboration would be 1986’s Super Mario Special, a port for the NEC PC-88 line of desktop computers. What ended up on that 5.25″ floppy sounded reminiscent of the Famicom original, but with a grand total of four colors (including black) and not a single scrolling screen in sight; Super Mario Special felt decidedly less than spectacular to play. Those eternally flickering sprites mixed with jarring blank screen transitions would never make it outside of Japan, so for a large swath of the world Mario would remain constrained to a gray plastic cartridge for years to come.
There are no shortage of ways to play Super Mario Bros. these days. Emulation in all of its various official and unofficial forms has taken care of that. Virtually everything with a processor more capable than the NES’s 6502 can play host to the Mushroom Kingdom, however, machines more contemporary with the NES still lacked access to the iconic title.
Enter the 2019 port of Super Mario Bros. for the Commodore 64 by [ZeroPaige]. A culmination of seven years work to port the game onto one of the most prolific computers of the eighties was a clear feat of brilliance and an amazing bit of programming that would have taken 1986 by storm. No pale imitation, this was Mario on the C64. Despite all of the nuance in recreating the jump-and-run model of the original paired with enveloping all eight sound channels of a dual SID chip setup, Nintendo saw fit to stifle the proliferation of this incredible 170 kB of software because they claim it infringes on their copyright.
In the last installment of “The $50 Ham” I built a common tool used by amateur radio operators who are doing any kind of tuning or testing of transmitters: a dummy load. That build resulted in “L’il Dummy”, a small dummy load intended for testing typical VHF-UHF handy talkie (HT) transceivers, screwing directly into the antenna jack on the radio.
As mentioned in the comments by some readers, L’il Dummy has little real utility. There’s actually not much call for a dummy load that screws right into an HT, and it was pointed out that a proper dummy load is commercially available on the cheap. I think the latter observation is missing the point of homebrewing specifically and the Hackaday ethos in general, but I will concede the former point. That’s why at the same time I was building L’il Dummy, I was building the bigger, somewhat more capable version described here: Big Dummy.