TechyMagThings

Friends, there will likely come a time in your life when you have trouble sleeping. When this happens, it may behoove you to do some writing, any kind of writing. But consider that a physical journal will force you to turn past pages you’ve already filled, which may leave you deflated if you happen to read them.

So the answer lies in a sort of journalistic deposit box. That’s basically what we have here. [Simon Shimel]’s Bee Write Back writerdeck was inspired by sleepless nights, so you know it’s effective. The form factor is so great for [Simon], in fact, that he has developed more apps and functions for it, including a Claude client.

Inside is a Raspberry Pi Zero 2w, and input comes from an Air40 keyboard with quite awesome low-profile key caps. The display is a 5.5″ AMOLED, which leaves just enough room for a pair of the cutest bees ever. Be sure to check out the short video below for the build guide to accompany the build guide (PDF), and head over to GitHub for the full details.

Want to go even smaller and BYOK? Here’s a cheap writerdeck with an e-ink display.

Thanks to [Kaushlesh Chandel] for the tip!

Although the number of uses for a 2009-era Mac Mini aren’t very long, using them to run new-and-upcoming operating systems like Haiku on would seem to be an interesting use case. This is what [The Phintage Collector] recently took a swing at, using both the 2024 Beta 5 release and a current nightly build. The focus was mostly on the 32-bit build, as this has binary compatibility with BeOS applications, but the 64-bit version of Haiku was of course also installed.

One of the main issues with these Mac systems is that they use EFI for the BIOS, so you’re condemned to either take your chances with the always glitchy CSM ‘classical BIOS’ mode, or to make Haiku and EFI get along. While for the 64-bit version of Haiku this wasn’t too much of a struggle, the 32-bit version ran into the problem that the 64-bit EFI BIOS really doesn’t like 32-bit software. After a while the 32-bit version of Haiku was thus abandoned for a later revisit.

With the 64-bit version a lot of things just work, though audio couldn’t be made to work even with a USB dongle, and there’s no hardware acceleration for graphics, so gaming isn’t really going to happen either. The positive thing here is probably that as a test system for 64-bit Haiku such a Mac Mini isn’t too crazy, it being just an Intel system with an Apple-flavor EFI BIOS.

If you’re into giving it a shot yourself, the video description page contains a lot of resources to consult.

At this point, we’ll assume you already know that four humans took a sightseeing trip around the Moon and made their triumphant return to Earth on Friday. Even if you somehow avoided hearing about it through mainstream channels, we kept a running account of the mission’s highlights stuck to the front page of the site for the ten days that the crew was in space.

On the assumption that you might be a bit burned out with space news at this point, we won’t bring up it up in this post… other than to point out that excitement for the lunar flyby has driven the number of simultaneous players of Kerbal Space Program to its highest count ever — nearly 20,000 armchair astronauts spent this weekend trying to cobble together their own rocket in honor of the Artemis II mission.

With so many folks focused on the Moon it would be the perfect time for a company to sneak out some bad news, which is perhaps why Amazon picked this week to announce they would be dropping support for Kindles released before 2012. Presumably there aren’t too many first and second generation Kindles still out there in the wild, but the 2012 cutoff does mean the first iteration of the Paperwhite will be one of the devices being put out to pasture come May 20th.

Amazon says the pre-2012 Kindles that are currently in user’s hands will still function, but they’ll no longer be able to purchase or download new books. The bigger issue is that you won’t be able to register these older devices after May. So if you have to factory reset your own Kindle, or want to buy one on the second hand market that’s already been wiped, you won’t be able to link it to your account to download books you’ve purchased.

Frankly, the idea that Amazon will no longer have their nose in these devices doesn’t bother us one bit. In fact, it sounds like an improvement over the status quo. If you own one of the device’s in question, now would be a fantastic time to download Calibre and start managing your own offline ebook library. In fact, even if your Kindle is new enough to not be affected by this change, you should still download it. Seriously, just use Calibre.

On the subject of software, an entry for XChat has recently popped up on Apple’s App Store. No, not that XChat. Instead of connecting to your favorite IRC server, the new mobile app will let you send messages to… whoever it is still actively using Twitter X. Confusingly, there’s also an XChat on the Google Play Store, but that appears to be a totally different thing altogether.

Finally, we’ve been seeing a lot of chatter online this weekend about France ditching Windows and switching over to Linux. While we applaud any mainstream push towards open source software, it’s worth digging into the details for this one. The directive says that the Interministerial Digital Directorate (DINUM) will be switching its desktop machines over to Linux, but that only represents a few hundred machines.

The experience gained during this roll-out will help shape a larger scale migration in the future, with the rest of the government asked to come up with a migration plan before the end of the year. When those other agencies, and the thousands of machines they use, will actually be penguin-powered is not clear. It’s possible they could come back and say a full migration would take a decade to complete.

So it’s certainly a step in the right direction, but it will likely be quite some time before any significant part of France’s infrastructure is divorced from the Redmond giant.

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.

Some might say the venerable Z80 doesn’t need another operating system, but [Scott Baker] obviously disagrees. He has come up with a brand new, from scratch OS called NostOS for the Z80-based RC2014 homebrew retrocomputer. [Scott] describes it as CP/M-like, but it’s not CP/M– in fact, it’s totally incompatible with CP/M–and has a few tricks of its own up its sleeve.

As you might expect of an operating system for this vintage of hardware, it is “rommable” — that is, designed to run from read-only-memory, and fit inside 64kB. It of course supports banking memory to go higher than that 16 bit limit, and natively supports common serial devices, along with the good old WD37C65 floppy controller to get some spinning rust into the game. Of course if you don’t have floppies you can plug in a compact flash card– try that with CP/M– or, interestingly Intel Bubble Memory. [Scott] has a soft-spot for bubble memory, which at one point seemed poised to replace both hard drives and RAM at the same time. We also appreciate that he included drivers for vacuum fluorescent displays, another forgotten but very cool technology. Back in the day, this operating system would have enabled a very cool little computer, especially when you take his implementation of text-to-speech with the SP0256A-AL2 chip. Fancy a game of talking Zork? Yes, he ported Zork, and yes, it talks.

The whole thing is, of course, open-source, and available on [Scott]’s GitHub. Unlike too many open-source projects, the documentation is top-notch, to the point that we could picture getting it in a three-ring binder with a 5 1/4 floppy on the inside cover. If you like video, we’ve embedded [Scott]’s walkthrough but his blog and the docs on GitHub have everything there and more if you’re not into rapidly-flickering-pixels as an information exchange medium.

[Scott] isn’t wedded to Zilog, for the record; this OS should run on an Intel 8080, perhaps like the one in the Prompt 80 he restored last year. 

Thanks to [Scott Baker] for the tip!

Although vapor-compression refrigeration is a simple concept, there are still a lot of details in the implementation of such a system that determines exactly how efficient it is. After making a few of such systems, [Hyperspace Pirate] decided to sit down and create a testing system that allows for testing of many of these parameters.

Some of the major components that determine the coefficient of performance (COP) of a heat pump or similar system include the used refrigerant, as well as the capillary tube diameter or expansion valve design. For the testing in the video three refrigerants are used: R600 (N-Butane), R134a (tetrafluoroethene, AKA Freon) and R290 (propane), with R134a being decidedly illegal in places like the EU. The use of R600 instead of R600A is due to the former allowing for a lower pressure system, which is nice for low-power portable systems.

The test rig has the typical fresh-from-the-scrap-heap look that we’re used to and love from [Hyperspace Pirate], but does exactly what it says on the tin, and is easy for any DIY enthusiast to replicate. Which compressor to pick for a specific refrigerant is also covered in the video, along with oil type and more.

For basic systems you’d use a simple capillary tube, whereas an airconditioner or similarly more complex system would use an adjustable valve design. With the rig you can test the efficiency of different tube diameters, with three sizes available in this version. Unfortunately the electronic expansion valve (EEV) that was going to be used didn’t get a chance to shine due to unforeseen events.

With the R134a and butane a COP of 2.0 – 2.5 was achieved when taking power factor into account, which was reasonable considering a compressor was used that targets R134a. Regardless, if you have ever felt like repurposing that old compressor from a fridge or AC unit, this might be a fun afternoon project.

Kiki bills itself as the “array programming system of unknown origin.” We thought it reminded us of APL which, all by itself, isn’t a bad thing.

The announcement post is decidedly imaginative. However, it is a bit sparse on details. So once you’ve read through it, you’ll want to check out the playground, which is also very artistically styled.

If you explore the top bar, you’ll find the learn button is especially helpful, although the ref and idiom buttons are also useful. Then you’ll find some examples along with a few other interesting tidbits.

One odd thing is that Kiki reads right to left. So “2 :* 3 :+ 1” is (1+3)2 not (23)+1. Of course, you can use parentheses to be specific.

If you are jumping around in the tutorial, note that some cells depend on earlier cells, so randomly pressing a “run” button is likely to produce an error.

Would you use kiki? There are plenty of array languages out there, although perhaps none that have such poetic documentation. Let us know if you have a favorite language for this sort of thing and if you are going to give Kiki a try.

If you want to try old school APL, that’s easier than ever.

There’s a long history of devices originally used for communication being made into computers, with relay switching circuits, vacuum tubes, and transistors being some well-known examples. In a smaller way, pneumatic tubes likewise deserve a place on the list; [soiboi soft], for example, has used pneumatic systems to build actuators, logic systems, and displays, including this latching seven-segment display.

Each segment in the display is made of a cavity behind a silicone sheet; when a vacuum is applied, the front sheet is pulled into the cavity. A vacuum-controlled switch (much like a transistor, as we’ve covered before) connects to the cavity, so that each segment can be latched open or closed. Each segment has two control lines: one to pressurize or depressurize the cavity, and one to control the switch. The overall display has four seven-segment digits, with seven common data lines and four control lines, one for each digit.

The display is built in five layers: the front display membrane, a frame to clamp this in place, the chamber bodies, the membrane which forms the switches, and the control channels. The membranes were cast in silicone using 3D-printed molds, and the other parts were 3D-printed on a glass build plate to get a sufficiently smooth, leak-free surface. As it was, the display used a truly intimidating number of fasteners to ensure airtight connections between the different layers. [soiboi soft] used the display for a clock, so it sits at the front of a 3D-printed enclosure containing an Arduino, a small vacuum pump, and solenoid valves.

This capacity for latching and switching, combined with pneumatic actuators, raises the interesting possibility of purely air-powered robots. It’s even possible to 3D-print pneumatic channels by using a custom nozzle.

Thanks to [Norbert Mezei] for the tip!