A few days ago the source code for the popular Winamp music player was released into the world, with as we reported at the time, a licence that left a lot to be desired. Since then it seems some of the criticism has caught up with the company, for not only have they modified their terms to allow forking, they’ve reacted to a bunch of claimed GPL violations by removing offending files. Perhaps How-To-Geek are right in describing it all as an absolute mess.
The forking amendment means that with luck we’ll start seeing a few modified players descending from the Winamp code, and it seems that the GPL violations are more embarrassing technicalities than show-stoppers, but we have to wornder whether or not this makes for something with any more than historical interest. Perhaps its value stands in a lesson for corporate entities in how not to release their source, which sadly we expect will be taken by other organisations as an excuse not to do so.
The software defined radio has opened up unimaginable uses of the radio spectrum for radio enthusiasts, but it’s fair to say that there’s one useful feature of an old-fashioned radio they lack when used via a computer. We’re talking of course about the tuning knob, because it represents possibly the most intuitive way to move across the bands. Never fear though, because [mircemk] has a solution. He’s converted a mouse into a tuning dial.
The scroll wheel on a mouse is nothing more than a rotary encoder, and can easily be used as a sort of tuning knob. Replacing it with a better encoder gives it a much better feel, so that’s what he’s done. An enclosure has the guts of a mouse, with the front-mounted encoder wired into where the scroll wheel would have been. The result, for a relatively small amount of work, is a tuning knob, and a peripheral we’re guessing could also have a lot of uses beyond software defined radio.
It’s not the first knob we’ve seen, for that you might want to start with the wonderfully named Tiny Knob, but it’s quite possibly one of the simplest to build. We like it.
As if there weren’t enough worrying global news stories already, today the British press and media have been full of a story involving the public WiFi networks at some major railway stations. Instead of being faced with the usual don’t-be-naughty terms and conditions page, commuters were instead faced with a page that definitely shouldn’t have been there.
Hackaday readers will immediately have guessed what is likely to have happened. This is probably more of a compromise of the page than of the network itself, and, indeed, the BBC are reporting that it may have come via an administrator account at Network Rail’s er… network provider. Fortunately, it seems the intent was to spread a political message rather than malware, so perhaps those travelers got off lightly. The various companies involved have all got the proverbial egg on their faces, and we’re glad we don’t work in the IT department concerned.
The question we find ourselves asking as we reflect upon this is: In crowded European commuter zones such as southern and central England, should events such as this come as a wake-up call to forgo WiFi and use a cellular data plan instead? Gone are the days when finding public WiFi was like having your own private high-speed connection, in a country blanketed by 4G and 5G networks using your phone as a hotspot is simply much faster as well as offering some security. Hackaday is written and edited on the road using a hotspot in all sorts of unlikely places. Do you do the same? Are Hackaday readers up for free public WiFi, or do you jealously guard your own connections? Let us know in the comments.
Do you live in the UK, have a VCR and capture card, and an interest in Teletext? [James O’Malley] needs your help! Teletext was, for many people around the world, their first experience of an electronic information system. The simple text and block graphics were transmitted on rotation as data bursts in the frame blanking periods of analogue TV broadcasts, and in an era of printed newspapers, they became compulsory reading. The UK turned off its old-style teletext over a decade ago with the switch to digital, but fragments of the broadcasts remain and can be painstakingly revived from period video recordings with the appropriate software.
This is where [James’] problem begins. Having recovered a very large archive of 1980s and 1990s VHS tapes, he’s come to the realisation that he’s bitten off more than he can chew, and that the archive needs to be in the hands of an individual, entity, or organisation which can give it the resources necessary to archive both the teletext and the programming that it contains. Can you help? Give the article linked above a read.
The 1990s seem to have reached that point at which they are once more considered cool, and ephemera of the decade has become sought-after. One of the unlikely software hits from the period was Winamp, the MP3 player of choice in an era when time spent on dodgy file sharing sites or peer to peer sharing would snag you almost any music you wanted. Decades later its interface is still widely copied, but now you can try the original again as its source code has been made available. It’s not what we’d call open source though, even though they seem to be making an effort to imply as much with phrases such as “opening up its source code“.
If you’d like to have a go with it you can snag a copy from this GitHub repository, and you’ll need a particular version of Visual Studio 2019 to build it. Any celebrations will be muted though by paragraph five of the Winamp Collaborative License, which prohibits distribution of modified versions or forks, and stipulates that only the official maintainers can distribute it. This doesn’t sound like open source to us, indeed it seems they’re just looking for community maintenance for free, which probably isn’t too surprising from a brand which went all-out to join the NFT bandwagon a couple of years ago.
So have a look for nostalgia’s sake if you want, but we’d suggest going for something more community driven if you want to do anything with it.
Opening up the device reveals a Tuya BT17L Bluetooth module, the hackable nature of which due to other projects prompted a port of a previous Find My project which provided open source access to the network. The result is as he describes, the world’s chunkiest key finder, and also we’re guessing the one with one of the longest battery lives too.
The European budget supermarkets are well known for their budget bargain aisles, and Lidl’s Parkside range has some surprisingly robust tools among it. They might not quite be up to replacing IKEA in the hacker source stakes, but those of us who live in countries served by them know to keep an eye out in the hope of fresh gems alongside those awesome AlpenFest apple crumble cakes. This one certainly isn’t the first Parkside hack we’ve seen.
Most of us have some form of an on-the-go toolkit, but how much thought have we put into its contents? \there’s a community of people who put a lot of thought into this, and EMF Camp have put up one of their talks from earlier in the summer in which [Drew Batchelor] sets out their manifesto and introduces tinytoolk.it, a fascinating resource.
The talk is well worth a watch, as rather than setting the tools you should be carrying, it instead examines the motivations for your kit in the firs place, and how to cull those which don’t make the grade. If an items seems to see little use, put a piece of tape with the date on it every time it comes out, to put a number on it. As an example he ended up culling a multi-tool from his kit, not because it’s not an extremely useful tool, but because he found everything it did was better done by other items in the kit.
It’s probable we’ll all look at our carry-around kit with new eyes after watching this, it’s certain that ours could use a few tweaks. What’s in your kit, and how could you improve it? Let us know in the comments.
Our community’s events are something special, bringing as they do an opportunity to meet and mingle with other hackers whether their field be hardware, software, or security, to share ideas, and to see some very cool projects. Here at Hackaday aside from our own Supercon and Hackaday Europe events we try to take in as many as we can over the year, and thus it’s always interesting to sot a new one. If you’re in north-west Europe next weekend, consider dropping by Hackfest, in the Dutch city of Enschede, right on the German border.
Looking at the program and the projects and workshops listed on the website we can see robotics, lockpicking, demoscene, retrocomputing, and plenty of open source. There are quite a few names which have featured at times here on these pages, something which certainly piqued our interest. Finding that it’s only 15 Euros for a weekend’s admission sealed the deal, and thus it’s time for Hackaday to break out the trusty Interrail pass once more and make the trek. Sadly many of Hackaday’s community will be too far away to join us, but if you’re close enough to make it then it’s one to consider.
It’s not uncommon for a new distro version to come out, and a grudging admission that maybe a faster laptop is on the cards. Perhaps after seeing this project though, you’ll never again complain about that two-generations-ago 64-bit multi-core behemoth, because [Dimitri Grinberg] — who else! — has succeeded in booting an up-to-date Linux on the real most basic of processors. We’re not talking about 386s, ATmegas, or 6502s, instead he’s gone right back to the beginning. The Intel 4004 was the first commercially available microprocessor back in 1971, and now it can run Linux.
So, given the 4004’s very limited architecture and 4-bit bus, how can it perform this impossible feat? As you might expect, the kernel isn’t being compiled to run natively on such ancient hardware. Instead he’s achieved the equally impossible-sounding task of writing a MIPS emulator for the venerable silicon, and paring back the emulated hardware to the extent that it remains capable given the limitations of the 1970s support chips in interfacing to the more recent parts such as RAM for the MIPS, an SD card, and a VFD display. The result is shown in the video below the break, and even though it’s sped up it’s clear that this is not a quick machine by any means.
The dulcet tones of a modem handshake may be a thing of the distant past for most of us, but that hasn’t stopped there being a lively hacking scene in the world of analogue telephones. Often that’s achieved using old devices resurrected from a parts bin, but sometimes, as with [Brian]’s USB modem, the devices are entirely new.
A surprise is that modem chips are still available, in this case the SkyWorks IsoModem chips. It uses an M.2 module format to allow the modem and support circuitry to be separated enough to place it in another project if necessary, along with a clear warning on the PCB not to put it in the identical-looking PC slot. It also comes with tips for experimenting if you don’t have access to a landline too, given that POTS is fast becoming a thing of the past itself in so many places.
If you’ve got nowhere to show off your modem, we’d like to suggest you try a hacker camp. There you’ll often find a copper network you’re positively expected to hack.
When the entry of a tech giant such as Apple into a market represents its liberation from exploitation, that market must be really broken, yet the reported FDA approval of the hearing aid feature in the latest AirPod earbuds seems to represent just that. The digital hearing aid business is notorious for its sharp sales practices and eye-watering prices, so for all Apple’s own notoriety the news might actually represent a leap forward for consumers in that sector. We have to ask though, if Apple of all people are now the Good Guys, where has the world of electronics gone so badly wrong?
Your grandparents decades ago would have had a simple analogue hearing aid if they had one, usually a small transistor circuit and perhaps with some kind of analogue filtering. Digital aids with DSP algorithms to pick out speech arrived some time in the 1990s, and from there evolved a market in which their high prices increasingly didn’t match the cost of the technology or software involved. At least in the UK, they were sold aggressively to older people as less cumbersome or better than the National Health Service aids, and if you had an older person in the family it was routine to see pages and pages of targeted junk mail offering dubious financial schemes to pay for them.
The question then, given that a modern hearing aid has a relatively cheap microcontroller and DSP at its heart, why has the open source community not risen to the challenge? The answer is that they have, though the Tympan seems an over-expensive trinket for what it is and the LoCHAid and Open Speech Platform seem to have sunk without trace. Can we do better?
Earlier this year Zilog stopped production of the classic 40-pin DIP Z80 microprocessor, a move that brought a tear to the eye of retro computing enthusiasts everywhere. This chip had a huge influence on both desktop and embedded computing that lingers to this day, but it’s fair to say that the market for it has dwindled. If you have a retrocomputer then, what’s to be done? If you’re [Dean Netherton], you create a processor card for the popular RC2014 retrocomputer backplane, carrying the eZ80, a successor chip that’s still in production.
The eZ80 can be thought of as a Z80 system-on-chip, with microcontroller-style peripherals, RAM, and Flash memory on board. It’s much faster than the original and can address a relatively huge 16MB of memory. For this board, he’s put the chip on a processor daughterboard that plugs into a CPU card with a set of latches to drive the slower RC2014 bus. We can’t help drawing analogies with some of the 16-bit upgrades to 8-bit platforms back in the day, which used similar tactics.
Your shiny new personal electronic device is likely to be designed solely as an app platform to run the products of faceless corporations, so the story goes, and therefore has an ever smaller hacking potential. Perhaps that view is needlessly pessimistic, because here’s [JP3141] with an example that goes against the grain. It’s an Apple Watch, being used as an ammeter. How it does that comes as the result of a delicious piece of lateral thinking.
Like many mobile devices, the device comes with a magnetometer. This serves as an electronic compass, but it’s also as its name might suggest, an instrument for sensing magnetic fields in three axes. With a 3D printed bobbin that slides over the watch, and a few turns of wire, it can sense the magnetic field created by the current, and a measurement can be derived from it. The software on the watch is only a simple proof of concept as yet, but it applies some fairly understandable high-school physics to provide a useful if unexpected measure of current.
We’re surprised to see just how many times the Apple Watch has appeared on these pages, but scanning past projects it was a cosmetic one which caught our eye. Who wouldn’t want a tiny Mac Classic!
In the early 1990s I was privileged enough to be immersed in the world of technology during the exciting period that gave birth to the World Wide Web, and I can honestly say I managed to completely miss those first stirrings of the information revolution in favour of CD-ROMs, a piece of technology which definitely didn’t have a future. I’ve written in the past about that experience and what it taught me about confusing the medium with the message, but today I’m returning to that period in search of something else. How can we regain some of the things that made that early Web good?
We All Know What’s Wrong With The Web…
It’s likely most Hackaday readers could recite a list of problems with the web as it exists here in 2024. Cory Doctrow coined a word for it, enshitification, referring to the shift of web users from being the consumers of online services to the product of those services, squeezed by a few Internet monopolies. A few massive corporations control so much of our online experience from the server to the browser, to the extent that for so many people there is very little the touch outside those confines.
Contrasting the enshitified web of 2024 with the early web, it’s not difficult to see how some of the promise was lost. Perhaps not the web of Tim Berners-Lee and his NeXT cube, but the one of a few years later, when Netscape was the new kid on the block to pair with your Trumpet Winsock. CD-ROMs were about to crash and burn, and I was learning how to create simple HTML pages.
The promise then was of a decentralised information network in which we would all have our own websites, or homepages as the language of the time put it, on our own servers. Microsoft even gave their users the tools to do this with Windows, in that the least technical of users could put a Frontpage Express web site on their Personal Web Server instance. This promise seems fanciful to modern ears, as fanciful perhaps as keeping the overall size of each individual page under 50k, but at the time it seemed possible.
With such promise then, just how did we end up here? I’m sure many of you will chip in in the comments with your own takes, but of course, setting up and maintaining a web server is either hard, or costly. Anyone foolish enough to point their Windows Personal Web Server directly at the Internet would find their machine compromised by script kiddies, and having your own “proper” hosting took money and expertise. Free stuff always wins online, so in those early days it was the likes of Geocities or Angelfire which drew the non-technical crowds. It’s hardly surprising that this trend continued into the early days of social media, starting the inevitable slide into today’s scene described above.
…So Here’s How To Fix It
If there’s a ray of hope in this wilderness then, it comes in the shape of the Small Web. This is a movement in reaction to a Facebook or Google internet, an attempt to return to that mid-1990s dream of a web of lightweight self-hosted sites. It’s a term which encompases both lightweight use of traditional web tehnologies and some new ones designed more specifically to deliver lightweight services, and it’s fair to say that while it’s not going to displace those corporations any time soon it does hold the interesting prospect of providing an alternative. From a Hackaday perspective we see Small Web technologies as ideal for serving and consuming through microcontroller-based devices, for instance, such as event badges. Why shouldn’t a hacker camp badge have a Gemini client which picks up the camp schedule, for example? Because the Small Web is something of a broad term, this is the first part of a short series providing an introduction to the topic. We’ve set out here what it is and where it comes from, so it’s now time to take a look at some of those 1990s beginnings in the form of Gopher, before looking at what some might call its spiritual successors today.
An ancient Firefox version shows us a Gopher site. Ph0t0phobic, MPL 1.1.
It’s odd to return to Gopher after three decades, as it’s one of those protocols which was for most of us immediately lost as the Web gained traction. Particulrly as at the time I associated Gopher with CLI base clients and the Web with the then-new NCSA Mosaic, I’d retained that view somehow. It’s interesting then to come back and look at how the first generation of web browsers rendered Gopher sites, and see that they did a reasonable job of making them look a lot like the more texty web sites of the day. In another universe perhaps Gopher would have evolved further to something more like the web, but instead it remains an ossifed glimpse of 1992 even if there are still a surprising number of active Gopher servers still to be found. There’s a re-imagined version of the Veronica search engine, and some fun can be had browsing this backwater.
With the benefit of a few decades of the Web it’s immediately clear that while Gopher is very fast indeed in the days of 64-bit desktops and gigabit fibre, the limitations of what it can do are rather obvious. We’re used to consuming information as pages instead of as files, and it just doesn’t meet those expectations. Happily though Gopher never made those modifications, there’s something like what it might have become in Gemini. This is a lightweight protocol like Gopher, but with a page format that allows hyperlinking. Intentionally it’s not simply trying to re-implement the web and HTML, instead it’s trying to preserve the simplicity while giving users the hyperlinking that makes the web so useful.
It feels a lot like the early 1990s Web, doesn’t it.
The great thing about Gemini is that it’s easy to try. The Gemini protocol website has a list of known clients, but if even that’s too much, find a Gemini to HTTP proxy (I’m not linking to one, to avoid swamping someone’s low traffic web server). I was soon up and running, and exploring the world of Gemini sites. Hackaday don’t have a presence there… yet.
We’ve become so used to web pages taking a visible time to load, that the lightning-fast response of Gemini is a bit of a shock at first. It’s normal for a web page to contain many megabytes of images, Javascript, CSS, and other resources, so what is in effect the Web stripped down to only the information is unexpected. The pages are only a few K in size and load in effect, instantaneously. This may not be how the Web should be, but it’s certainly how fast and efficient hypertext information should be.
This has been part 1 of a series on the Small Web, in looking at the history and the Gemini protocol from a user perspective we know we’ve only scratched the surface of the topic. Next time we’ll be looking at how to create a Gemini site of your own, through learning it ourselves.
Core memory, magnetized memory using tiny magnetic rings suspended on a grid of wires, is now more than five decades obsolete, yet it exerts a fascination for hardware hackers still. Not least [Andy Geppert], who’s made a nibble, four bits of it, complete with interactive LED illumination to show state. Best of all, it’s on a badge Simple Add-On (SAO) for fun and games at your next hacker con.
Aside from it being a fun project, perhaps the most interesting part comes in the GitHub repository, where can be found the schematic for the device. He’s built all the drive and sense circuitry himself rather than finding an old-stock core memory driver chip, which gives those of us who’ve never worked with this stuff the chance to understand how it works. Beyond that it takes input from the Stemma or SAO ports to a GPIO expander, which provides all the lines necessary to drive it all.
For all the advances in digital photography, there remains a mystique for photographers and filmmakers about chemical film. Using it presents an artistic and technical challenge, and it lends an aesthetic to your work which is difficult to find in other ways. But particularly when it comes to moving pictures, how many of us have ever ventured beyond the Super 8 cartridge? If you’re not lucky enough to have a Spielberg budget, [Stand-Up Maths] is here with a video taking the viewer through the various movie film formats. He claims it’s the first video shot for YouTube in 35mm, and given that his first point is about the costs involved, we can see why.
In particular it serves as an introduction to the various film terms and aspect ratios. We all know what full frame and IMAX are, but do many of us know what they really mean in camera terms. A particularly neat demonstration comes when he has two cameras side by side with the same stock as a split screen, one 35mm and the other 16mm. The cheaper smaller framed format is good quality, but using a profession resolution chart you can see some of the differences clearly. The full film is below the break, and we’d suggest you watch it in the full 4K resolution if you are able to.
If you follow the world of clean energy, you will probably have read all about the so-called hydrogen future and the hydrogen economy. The gas can easily be made from water by electrolysis from green solar electricity, contains a lot of stored energy which is clean to recover, and seems like the solution to many of our green energy woes. Sadly the reality doesn’t quite match up as hydrogen is difficult to store and transport, so thus far our hydrogen cars haven’t quite arrived. That hasn’t stopped researchers looking at hydrogen solutions though, and a team from ETH Zurich might just have found a solution to storing hydrogen. They’re using it to reduce iron oxide to iron, which can easily release the hydrogen by oxidation with water.
Their reactor is simplicity itself, a large stainless steel tank filled with powdered iron ore. Pump hydrogen into it and the iron oxide in the ore becomes water and iron which forms the storage medium, and retrieve the hydrogen later by piping steam through the mixture. Hydrogen generated in the summer using solar power can then be released in the winter months. Of course it’s not perfectly efficient, and a significant quantity of energy is lost in heat, but if the heat is recovered and used elsewhere that effect can be mitigated. The hope is that their university might be benefiting from a pilot plant in the coming years, and then perhaps elsewhere those hydrogen grids and cars might become a reality. We can hope.
For almost as long as there have been microcomputers, there have been attempts with varying success to make tiny handheld microcomputers. Sometimes these have been very good, and other times they’ve missed the mark in some way. Latest to find its way to us is the CL-32 from [Moosepr], it’s a handheld computer with an ESP32 as brains, an electronic paper display, and a QWERTY keyboard in its smart printed case.
The hardware is relatively standard, save for the keyboard which is a dome-switch design in which the membrane carrying the domes is hand-made. We like this, and don’t think we’ve seen anyone else doing that. Expansion is taken care of by a novel socket arrangement in which boards nestle in a recess in the surface. Some experimentation was required as always to drive the display, but the result is a functional computer.
Sadly there’s little detail in terms of what the software will be, and no hardware files as yet. But what we can see is promising enough to make this one to watch, so we’ll look forward to what they come up with. If an ESP32 OS is a problem, there’s always badge.team, who have been continuously improving theirs since 2017.
We’re guessing most readers can cite things from their youth which gave them an interest in technology, and spurred on something which became a career or had a profound impact on their life. Public engagement activities for technology or science have a crucial role in bringing forth the next generations of curious people into those fields, and along the way they can provide some fun for grown-ups too.
A case in point is from NASA’s Landsat engagement team, Your Name In Landsat. Type in a text string, and it will spell it out in Earth features seen by the imaging satellites, that resemble letters. Endless fun can be had by all, as the random geology flashes by.
No text emojis, boo hiss!
In itself, though fun, it’s not quite a hack. But behind the kids toy we’re curious as to how the images were identified, and mildly sad that the NASA PR people haven’t seen fit to tell us. We’re guessing that over the many decades of earth images there exists a significant knowledge base of Earth features with meaningful or just amusing shapes that will have been gathered by fun-loving engineers, and it’s possible that this is what informed this feature. But we’d also be curious to know whether they used an image classification algorithm instead. There must be a NASA employee or two who reads Hackaday and could ask around — let us know in the comments.
Conectar
