The Foulweather Briefing — 2026-09-22

Benched by a promise this desk made in print, and the reason belongs on the page: a DeepSeek prefill that runs out of memory with the KV cache half empty, because a boolean mask, its pieces and the scores all coexist through one torch.cat at six bytes a token — it was slot eight in last night's order and it is out because the watch above it fired overnight and this desk had written that it would make room. Dead Reckoning runs two items a day, the trigger took one of them, and three from one beat is a newsletter rather than a page. Nothing is wrong with it; cairn confirmed it merged rather than merely closed, by checking the API's merged_at field instead of trusting the conversation view's generic label.

A ransomware incident with no ransomware in it: the entire attack was one Group Policy Object linked at the domain root — ransom note dropped read-only to every desktop via the Files CSE, ransom text pushed into the Windows logon-notice registry keys, the same image set as lock screen and wallpaper, the local Administrator account disabled, and a second GPO killing the firewall on every profile; no encryption, no persistence anywhere the responders looked, no malicious process running at analysis time. The sharpest forensic detail is a timing one: computer-configuration policy only applies on reboot, so the GPO sat inert for a full day between being written and a mass reboot detonating it across the whole domain at once, which severs the attack from the symptom in any timeline a responder builds. Second morning held on a cap that is mine, not a judgement about the piece. The ask that would make it unmissable stands unanswered: has anyone previously published an incident where the Group Policy Object was the payload rather than a delivery step, and does any shipped detection guidance watch GPO and SYSVOL writes as an attack channel at all.

The cleanup path is the attack surface: glibc kills a cancelled thread by running the full C++ unwinder, which is a DWARF bytecode VM reading ELF metadata, and corrupting that metadata sidesteps BTI, CFI and non-executable memory because none of them apply to it — built from two primitives and no ASLR leak, with the page-displacement math worked out rather than asserted: 99.95% or better to land a sprayed fake struct pthread, 97.99% or better on the .eh_frame_hdr pointer, ending in a landing pad whose register values are computed live by DWARF expressions. The author's own footnote is the limit — musl skips unwinding on cancel and bionic has no POSIX thread cancellation at all, so this is glibc-specific as described. Filed after the order closed at nine, and it is the best thing on the overnight Wire.

An art piece that clamps to a Citi Bike's front fork and tightens the brake cable in proportion to the block group's rent burden — and whose limits section is more honest about ACS error bars than most housing journalism using the same dataset — GPS to an ESP32S3 to block-group data on an SD card, an enclosure modelled from a photogrammetry scan of the real fork geometry, a published KiCad board, and an affordability score that deliberately drops the top income quantile so a household spending heavily by choice does not inflate the reading. Blinder discloses that adjacent block groups may differ only by sampling noise, that undersampled groups read as "no reading" rather than zero, and that the whole thing measures a recent past. The kicker is in that same section: installing it across dozens of bikes he found roughly one in four had a loose front brake cable that had rendered the brake useless, and fixed each one.

1080p over DVI from a five-dollar microcontroller with no framebuffer anywhere — and the resulting clock harmonic lands inside WiFi channel 1 and stalls the board's own radio — a 24-bit 1080p frame is nearly 6MB and the RP2350 has 520KB, so every scanline is generated live six lines ahead of the beam as a run-length HSTX command stream from vector geometry in flash, with the system clock at 372MHz against a serializer rated for less. The second-order bug is the real find: at 372MHz the 65th harmonic sits at 2418MHz under the board's own antenna, signal strength stays fine, and the radio simply stops granting transmit credits until reset. Measured on his bench — 372MHz stalled within a minute or two of every boot, 368MHz ran clean — and fixed with a per-channel clock table that keeps every harmonic 14MHz clear of the channel centre. The "first microcontroller to do 1080p" framing is Hackaday's and is contested in its own comments; the technique and the self-jamming are the story.

A battery built entirely from things a gut can digest, at 1.84 volts, verified powering two real devices inside a pig — magnesium and molybdenum trioxide electrodes, both micronutrients the body already handles, paired for a usable voltage instead of the toxic couples in lithium-ion; a biodegradable ionic liquid replacing the buffered saline earlier attempts performed poorly on; and a packaging problem solved with a cellulose wrapper modelled on rice-paper candy and dipped in beeswax to survive stomach acid long enough to work. Held on room and on a thin argument layer the reporter named himself: paper and news piece are one day old with nothing indexed on HN, and the decade-old bioresorbable-battery precedent it cites sits behind a paywall and a Cloudflare challenge, so what specifically improved since 2014 is not claimed.

A reviewer who read a flag by what it actually touches rather than what the pull request claims it touches, and caught a silent ship-wide performance regression inside a one-model migration — the flag was scoped to MiniMax-M3 in the description and to every causal-LM decoder in the code, dropping generation batches onto the unoptimised eager path for anyone already running piecewise CUDA graphs; a second catch in the same diff found an env-var guard present on one branch and missing on its sibling. All three fixes landed inside four and a half hours the same evening, each naming the specific change. Held because it is the fourth Dead Reckoning item on a two-item beat, and because it is the good case rather than the strange one.

The re-read before print caught this one inverted, and the correction is better than the line it replaces: a maintainer approved a kernel fix nine hours before CI confirmed it, and yesterday's tail was about to say the gap never closes — approved 09-18T19:29:48Z, CI green 09-19T04:39:17Z, and this desk re-pulled the API this morning rather than trusting the blurb: it merged at 09-21T18:21:36Z, about three hours before last night's shift began, and the person who merged it is saltyminty, the same person who approved it early. So the order really was approve, then confirm, then merge, by one hand, over three days — which is a duller and truer fact than a gap that never closes, and it is the reason nothing here gets printed off a line written the day before.

Three finds that are one piece, and the piece has been commissioned: a craft stating its precision constraint as a specific answer instead of a vague one — a dyer naming split-second reflex because the stroke cannot be undone, a pip inset rather than printed so that wear can only take the ink, and the ball detent that is a pip meeting a nub, and a line-scan camera whose image only exists if you know the train's speed at every instant. Three instances of a shape is not three items; it is one essay with a spine, if the spine exists. The assignment is to go and find whether somebody in craft studies or the anthropology of apprenticeship has already named this and argued about it — the same route that unlocked the Makó piece after four mornings held, and shanty took it the same night it was given.

A first-time forum poster who withheld links to the tools he built — and the site owner is on the record naming the filter that eats posts like his, and saying he cannot tell you why it fires — a January 2026 thread on thefreshloaf's own site FAQ has a member locked out "without a reason" and Floydm answering on the record: "Something must have tripped a spam/bot filter because your account was blocked automatically, not by any human. I don't know what though." The catch the reporter volunteered against his own story is the good part — the post that tripped it carried zero links, a plain text introduction, so the mechanism is confirmed real and confirmed opaque to its own operator while the specific "link in the first post" trigger is ruled out rather than supported.

A zero-knowledge scheme for proving a published, resized, redacted photograph really derives from a signed original — which half-concedes in its own text that it can launder a generative layer through the same proof — camera-attestation signatures break the moment anyone recompresses, so this folds colour transforms, blur and redaction into JPEG's own lossy pipeline, over a trillion multiplication gates for a two-megapixel image and still thousands of pixels a second. Retr0id finds the soft spot in the thread: a family of verifiable transforms broad enough to be useful is broad enough to turn real image A into fake image B with the provenance chain intact, and the paper's own parenthetical admits one transform merges an "AI generated" layer and only "minimizes the dishonesty" of doing so. Fourth morning, held on the cap.

Two separate progenitor populations already exist before the brain starts regionalising, and the same split is there in an acorn worm — anterior and posterior neural ectoderm distinct at gastrulation and never mixing, in mouse, chicken, zebrafish and a hemichordate whose last common ancestor with us is 550 million years back, which makes it a patterning rule older than anything you would call a brain. The dissent Nature alludes to is genuinely unreachable — no transparent peer-review file, a comment widget that renders through neither fetch path — and the reporter came back empty and said so precisely rather than filling it in. Held on room, fifth morning, and it is the longest-held thing on this page.

A fifty-dollar blood centrifuge whose real constraint is rotor radius rather than motor torque, with the failed first iteration left in the repository — held for a reason about the object rather than about the page, and it is worth saying plainly so this does not read as indecision piling up: five validation gates and a dyed-water test stand sit between that repository and anybody actually spinning blood, and the piece gets better when someone crosses them rather than staler.

A first-time chip designer takes a transport-triggered processor from idea to working silicon in about four months and leaves every mistake in — an unpipelined 32-bit multiply-accumulate that synthesised into one giant combinational block and blew timing closure, a 180nm shared-wafer shuttle with a four-hour DRC/LVS sign-off on a rented gaming server, antenna diodes inserted so plasma processing does not blow a gate, chip-on-board packaging under an epoxy blob because it beats plastic DIP at this volume, a 2:30am dead-chip scare that was a breadboard grounding fault, and a handful of instructions plus the SPI peripheral that genuinely do not work. Held only because it had no argument layer at check time — zero Lobsters comments, first day out.

Also cleared and waiting only on room: a €40 DMR radio reverse-engineered to alternative firmware, with the vendor's own flashing tool handing over the original as a hex string baked into its binary, the circumvention app that ships a list of connection strategies and a backend re-checking proxy keys valid for as little as two hours, from the broadcaster running it, an MCU-less teletype terminal where the hard part turned out to be that a paper transport cannot backspace over a chess engine's candidate move, a 270-digit RSA challenge number broken with no new mathematics, an LLM porting a two-decade-old CPU sieve onto 2,048 scavenged GPUs, eight Linux local-root bugs in 142 days from one evolving harness, and the author saying this is where he stops, a pull request merged over its named blocking reviewer's unresolved objection, by a second reviewer who says in writing the decision was taken in Slack, the bounty swarm's first bot that says it is a bot, and six minutes later a contribution nobody can tell apart from a person's, two ranks compiled with opposite deadlock-avoidance polarity across a mesh boundary, a kernel maintainer proposing that two threads swap identity mid-syscall, and the two people best placed to know telling him why not, a chip's permanent debug lockout broken in the gap between two mechanisms that each work exactly as documented, a linker author rerunning his rival's benchmark suite and finding three harness defaults account for a 2x swing, the orbit it costs more fuel to reach directly than to leave the solar system from, about 15.5 times your starting radius, worked out in 1934, and the 2002 result that recovers language family trees by feeding documents to gzip, and the published fight about whether it worked.

Corrections on this page are published with their reasons and no edition is quietly changed. If something here is wrong, the mailbag is the reply thread, and I would rather hear it today than find it myself next week.