TechyMagThings

Someone calls you at work and says, “Don’t tell anyone, but…” If you are like most people, there are one or two people you will pass it along to with the same admonishment. In fact, they are probably repeating it from someone else, and you are on their list of two people. So for really big secrets, you need a way to spread the secret out so that no one has any real information about the secret, but a certain number of people together can decode it. As [neeaj] explains in a recent post about Shamir’s Secret Sharing, [Adi Shamir] (the S in RSA encryption) devised a way to do this very well in 1979, and the core concept is very easy to understand.

The explanation works with geometry. The equation for a line is y=mx+b, where m is the slope and b is the y-intercept (that is, where the line touches the y-axis when X is 0. An infinite number of lines cross the Y axis at, for example, 10. The line y=3x+10 does, and so does the line y=-1.41x+10. You can’t guess the b value from just the slope, because any slope will satisfy the equation.

So suppose the secret number is 10. I can pick a random slope and generate points on it. Like the y-intercept, any number of equations might satisfy that point. Let’s pick a random slope of 2 just to make the math easy. Our real equation is y=2x+10. Let’s pick a random X of 100 and tell one person their part of the secret is (100,210). That matches our equation, of course, but it also matches y=4x-190 and y=x+110, along with an infinite number of other lines.

To know the actual equation, you need at least two points. So let’s pick x=25 and tell another person that their part of the secret is (25,60). Now, if those two people compare notes, you can find the secret number by solving the two equations:

210=100m+b and 60=25m+b

The second equation is the same as 240=100m+4b, and you can subtract the first one from that:

30=3b
10=b

You can hand out any number of points to any number of people. Any two of them can recover the secret number. If you need to require more people to unlock the secret, you just go up in order. A parabola equation, for example, requires three points. A cubic takes four, and so on.

In reality, practical implementations take a polynomial, not a graph. But the elegant idea is the same. Not the first time we’ve heard of this algorithm. Reminds us of how a nuclear launch requires multiple keys.

Amidst the ongoing RAM & storage apocalypses, Mad Max-esque scenes are unsurprisingly developing, with the eMMC recycling project by [Chase Fournier] from a pair of XBox One S (‘XBone’) mainboards being just one more example. These mainboards come equipped with a 5 GB eMMC chip installed, alongside 8 GB of DDR3.

Removing the eMMC chips isn’t that complicated and after some reballing fun the chips were both installed on a carrier board with a Norelsys NS1081 controller IC. This provides a USB 3.0 interface and can connect to up to four SD or eMMC memories, with here just two channels used.

Although the eMMC testing device didn’t seem too happy with either chip, after mounting them on the PCB the controller could be programmed and saw both eMMC packages for a grand total of 10 GB storage.

Sequential read performance in CrystalDiskMark was about 140 MB/s while write performance was about 64 MB/s, which is zippy enough for smaller files. Not that you can store more than 10 GB on this USB drive anyway.

Turning the DDR3 ICs on the mainboard into proper DIMM or SODIMM sticks would also be an idea, as even such older memory tech keeps ramping up in demand. As for the XBone X variant with its 12 of GDDR5, that’s probably a harder proposition to repurpose, but recycling old consoles suddenly has become a lot more exciting.

The fjords of Norway are world famous for their beauty, but even though the word itself is Norwegian, there are fjords all over the world in areas that used to be covered in glaciers. One of these areas is the Pacific Northwest of North America, we herit’s actually possible to travel by boat from the Seattle area all the way into Alaska without going to the Pacific Ocean, and although plenty of people make this journey by boat, [Matt] is planning on doing this journey on a jet ski with a custom camper on the back.

Normally a jet ski wouldn’t be the ideal platform for a multi-day on-boat adventure because of their size, but [Matt] found perhaps the largest jet ski ever made and he got a deal on it since it had previously been wrecked. Once he repaired the hull damage, he cut a sheet of plywood in half and put a hinge in the middle so it can unfold over the top of the jet ski but fold it away when he’s traveling. With the basic concept in place he took it right out on the water to a campsite before finalizing the construction of the rest of the tent, including the installation of a door, a window, and some interior lighting.

During that first night, a storm cropped up and pushed the craft out to shore while [Matt] was sleeping, so after realizing, waking up, and motoring back to shore, he made sure to tie the craft to a rock to avoid similar situations before going back to sleep. But besides some motion sickness which prevented him from cooking inside his camper, the rest of the adventure went off without a hitch. Before taking it on the Inside Passage he has been thinking of a few improvements like outriggers to keep it from rocking while he sleeps. [Matt] is no stranger to unusual camper builds, though, we recently featured his other camper which is an electric car converted to explore abandoned railroads.

While designing anything for operation in space has its challenges, there is at least one thing that is more of a problem for objects in Earth orbit than for deep-space probes: atomic oxygen. We like oxygen because we need it to live, but it is also highly reactive as a single atom. Luckily, on Earth, most of what we breathe is O₂. [Space Daily] talks about the challenges of the International Space Station dealing with the “space weather” of atomic oxygen in low Earth orbit.

Part of the problem is that even when we know better, we tend to think of the atmosphere coming to an abrupt end and space being a hard vacuum. But in reality, the atmosphere gradually dissipates, and at “only” 400 km above the Earth, the Space Station is really flying through a very thin atmosphere.

To compound the problem, this is above the ozone layer, so the Sun’s UV light rips O₂ into single oxygen atoms. Over time, these free oxygen atoms can affect many parts of a spacecraft exposed to them. Engineers first noticed that materials recovered from spacecraft had more damage and changes to material properties on the pieces facing the direction of travel. NASA has spent years testing different materials by mounting trays of different material samples outside the ISS.

Carbon-based polymers take a big hit from atomic oxygen exposure. Polymide film is frequently used, but it erodes with exposure. Carbon composites also lose mass. Other materials change in other ways. For example, an optical surface may roughen with exposure.

The usual answer is to over-design for mission objectives or to cover certain polymers with coatings like silicon dioxide or aluminum oxide, which are not as reactive to free oxygen. For a long-duration mission like the ISS, you may have to pay special attention to the materials in use. Very low satellites also need special care, as there is more oxygen in lower orbits.

There are other effects, too, such as extreme thermal cycles, debris strikes, and other indignities that space-traveling materials must withstand. But in deep space, atomic oxygen is a rare issue. Until, at least, we go somewhere else that has a lot of oxygen.

The topic of downstream and upstream is an important one in the Linux ecosystem, where from one base distribution you can go many layers of distros deep before even looking at all the other base distributions. Within that veritable jungle you get questions about who is responsible for packaging software, where to report bugs found with a specific application, as well as what ‘LTS’ truly means in a consumer context. These and other points are raised in a recent video by [Brodie Robertson], with many examples of things going tragically wrong.

There’s a good argument to be made that ultimately it is the distro that is responsible for the software that they provide via their repositories. As [Brodie] shows in the video, there are a few cases where an ‘LTS’ distro uses an old version of some software that contains a bug that has been fixed a while ago, so reporting it to the developer is rather pointless, while the distro maintainers should fix it with backporting of patches or updating the version.

From an end user experience this also makes the most sense, as in the end they just want to have the Windows experience of downloading a proverbial installer, clicking through whatever dialogs pop and have working software. If the software is provided via the distro, it is their responsibility, the same way that you contact the developer if you get a DEB or RPM from a GitHub project page and it doesn’t work.

This current Linux Chaos Vortex can be called a major issue when e.g. FreeBSD has no such upstream/downstream issues, with cross-platform installers being basically impossible on Linux ever since the Linux Standard Base effort died.

Perhaps Linux will get a distroless future, however, which may finally herald that Year of the Linux Desktop.

Although resistors are hardly among the most exciting components, they are arguably one of the most important ones, as anyone who has done any amount of circuit design and debugging can attest to. So too with a single carbon resistor in a vintage Metrix oscilloscope that [CuriousMarc] recently repaired. After recapping the board there was still a major issue that got traced down to said resistor. After replacing it with a fresh resistor obviously this meant doing an autopsy to see why the old resistor had failed.

The 20 kOhm-rated resistor looked fine on the outside, with no obvious damage or discoloration, but it measured around 0.843 MOhm. To get to the insides [CuriousMarc] asked his friend [TubeTime] on how to proceed. The answer here was sandpaper and a lot of patience, and thus the experiment to see how much sanding it takes to get to the core of a fairly big resistor commenced.

Ultimately the insides were revealed, and they turned out to be rather interesting, with what looked like a glass tube filled with what would be the carbon-laden material between the two lead terminals. From poking around a bit at these insides it would appear that the failure mode was a degraded contact between these terminals and the carbon material. Considering that this resistor is many decades old and has gone through many thermal cycles and potentially various kinetic events some fractures are probably to be expected.

Perhaps most fascinating is the construction of this carbon resistor that looks to be a step above that of the average carbon resistor that [TubeTime] has taken apart over the years.

One simple screening tool for cognitive impairment is the clock-drawing test (CDT): the patient is provided with a printed circle and asked to draw a clock face with the hands pointing to a certain time. Depending on how the clock is drawn, this could indicate a variety of different disorders, particularly dementia, with a particular deformity in the drawing sometimes pointing to a specific issue. These failed tests inspired [John Silvia] to create a clock with a unique, disordered face.

The numerals in this clock face are placed exclusively along the right half of the clock (in the test, this can be a sign of damage to the right parietal lobe, or of executive dysfunction caused by dementia), and out of order. The hour hand is controlled by a servo motor, and the minute hand is mounted on a separate, commercially-purchased clock mechanism on the left-hand side of the face.

The frame for the clock and the face are 3D-printed, and the servo motor is controlled by an ESP32-C3 with an RTC module. To minimize power draw, a MOSFET disconnects the servo motor from power except for the once-per-hour position update. Once per month, the ESP32 connects to Wi-Fi to synchronize to NTP time, otherwise remaining in a low-power state – even its indicator LEDs are disconnected to save power. These efforts paid off: when the servo isn’t active, it draws only about 160 µA, and a set of three AA NiMH cells lasts about a year.

Since the servo motor draws most of the power budget, it wouldn’t make much difference, but the ESP32’s co-processor can also be used for ultra-low-power projects. For a happier take on a drawing-related clock, check out one of these projects.