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.
We’re back! This week Jonathan chats with Mattias Wadman and Michael Farber about JQ! It’s more than just a JSON parser, JQ is a whole scripting language! Tune in to find out more about it.
Continue reading “FLOSS Weekly Episode 842: Will The Real JQ Please Stand Up”
When do you think the first podcast occurred? Did you guess in the 1890s? That’s not a typo. Telefonhírmondó was possibly the world’s first true “telephone newspaper.” People in Budapest could dial a phone number and listen to what we would think of now as radio content. Surprisingly, the service lasted until 1944, although after 1925, it was rebroadcasting a radio station’s programming.
The whole thing was the brainchild of Tivadar Puskás, an engineer who had worked with Thomas Edison. At first, the service had about 60 subscribers, but Puskás envisioned the service one day spanning the globe. Of course, he wasn’t wrong. There was a market for worldwide audio programs, but they were not going to travel over phone lines to the customer.
The Hungarian government kept tight control over newspapers in those days. However, as we see in modern times, new media often slips through the cracks. After two weeks of proving the concept out, Puskás asked for formal approval and for a 50-year exclusive franchise for the city of Budapest. They would eventually approve the former, but not the latter.
Unfortunately, a month into the new venture, Puskás died. His brother Albert took over and continued talks with the government. The phone company wanted a piece of the action, as did the government. Before anything was settled, Albert sold the company to István Popper. He finalized the deal, which included rules requiring signed copies of the news reports to be sent to the police three times a day. The affair must have been lucrative. The company would eventually construct its own telephone network independent of the normal phone system. By 1907, they boasted 15,000 subscribers, including notable politicians and businesses, including hotels. Continue reading “The World’s First Podcaster?”
It is a good day for design review! Today’s board is the MuBook, a Lattepanda Mu SoM (System-on-Module) carrier from [LtBrain], optimized for a NAS with 4 SATA and 2 NVMe ports. It is cheap to manufacture and put together, the changes are non-extensive but do make the board easier to assemble, and, it results in a decent footprint x86 NAS board you can even order assembled at somewhere like JLCPCB.
This board is based on the Lite Carrier KiCad project that the LattePanda team open-sourced to promote their Mu boards. I enjoy seeing people start their project from a known-working open-source design – they can save themselves lots of work, avoid reinventing the wheel and whole categories of mistakes, and they can learn a bunch of design techniques/tips through osmosis, too. This is a large part of why I argue everyone should open-source their projects to the highest extent possible, and why I try my best to open-source all the PCBs I design.
Let’s get into it! The board’s on GitHub as linked, already containing the latest changes.
I found the very first review item when downloading the repo onto my computer. It took a surprising amount of time, which led me to believe the repo contains a fair bit of binary files – something quite counterproductive to keep in Git. My first guess was that the repo had no .gitignore for KiCad, and indeed – it had the backups/ directory with a heap of hefty .zips, as well as a fair bit of stuff like gerbers and footprint/symbol cache files. I checked in with [LtBrain] that these won’t be an issue to delete, and then added a .gitignore from the Blepis project.
When you think of neon, you might think of neon signs or the tenth element, a noble gas. But there was a time when neon bulbs like the venerable NE-2 were the 555 of their day, with a seemingly endless number of clever circuits. What made this little device so versatile? And why do we see so few of them today?
Neon’s brilliant glow was noted when William Ramsay and Morris Travers discovered it in 1898. It would be 1910 before a practical lighting device using neon appeared. It was 1915 when the developer, Georges Claude, of Air Liquide fame, received a patent on the unique electrodes suitable for lighting and, thus, had a monopoly on the technology he sold through his company Claude Neon Lights.
However, Daniel Moore in 1917 developed a different kind of neon bulb while working for General Electric. These bulbs used coronal discharge to produce a red glow or, with argon, a blue glow. This was different enough to earn another patent, and neon bulbs found use primarily as indicator lamps before the advent of the LED. However, it would also find many other uses.
We lost a true legend this week with the passing of NASA astronaut Jim Lovell at the ripe old age of 97. Lovell commanded the ill-fated Apollo 13 mission back in 1970, and along with crewmates Jack Swigert and Fred Haise — along with just about every person working at or for NASA — he managed to guide the mortally wounded Odyssey command module safely back home. While he’s rightly remembered for the heroics on 13, it was far from his first space rodeo. Lovell already had two Gemini missions under his belt before Apollo came along, including the grueling Gemini 7, where he and Frank Borman undertook the first long-duration space mission, proving that two men stuffed into a Volkswagen-sized cockpit could avoid killing each other for at least two weeks.
An old friend of mine at my hackerspace introduced me to the concept of Prototype Zero: The Version that Even Your Own Sweet Mother Isn’t Allowed to See. The idea is that when you’re building something truly new, or even just new to you, your first take will almost always be ugly, and nothing will work the way it will by the time you make your second one. But it’s also important to the exercise that you see it all the way through to the end if you can.
I’m reminded of this after seeing a marvelous video by [Japhy Riddle] where he discusses his Prototype Zero of the Tape-Speed Keyboard. About halfway through the video he says that he would have done it totally differently if he knew then what he knows now: the hallmark of Prototype Zero. Yet he finishes it up, warts and all, documents it, and plays around with all of its possibilities. (Documenting it publicly isn’t part of the Prototype Zero method.)
I don’t think that [Japhy] is going to make a Prototype 1.0 out of this project, but I could be wrong; he seems to be content with having scratched the variable-speed tape itch. But if he did want to, he’s learned all of the gotchas on the engineering side, and found out exactly what such an instrument is capable of. And this loops back to the importance of getting Prototype Zero finished. You may have learned all of the tricks necessary to build the thing even before you’ve put the last screw in, but it’s when you actually have the thing in your hands to explore that you get the ideas for refinement that you simply can’t think up when it’s still just a concept.
Don’t be afraid to make your prototype quick and dirty, because if it ends up too dirty, you can just call it Prototype Zero. But don’t be tempted by the siren’s song of the 80% finished prototype either. Exploring putting Prototype Zero into use is its real purpose.
Elliot and Dan got together this week for a review of the week’s hacking literature, and there was plenty to discuss. We addressed several burning questions, such as why digital microscopes are so terrible, why computer systems seem to have so much trouble with names, and if a thermal receipt printer can cure ADHD.
We looked at a really slick 5-axis printer that COVID created, a temperature-controlled fermentation setup, and a pseudo-Mellotron powered by a very odd tape recorder. We also learned little about designing 3D printed parts with tight tolerances, stepping a PC power supply up to ludicrous level, and explored a trio of unique entries for the One Hertz Challenge.
And for the Can’t Miss section, we looked at what happens to planes when they get hit by lightning (and how they avoid it), and say goodbye to the man who launched a lot of careers by making model kits.
It was also exciting to learn that the first day of Supercon is Halloween, which means a Friday night sci-fi cosplay party. It’s gonna be lit.
