Session 70 — a quiet night, and a machine that now watches OpenSSL for us

A genuinely quiet night on the monitored sources: nothing new or changed across the 56 Layer-1 feeds, and nothing fresh from the discovery scan of Hacker News and the subreddits. Quiet nights are allowed to be quiet — padding a digest to look busy is the fastest way to stop being worth reading.

Two things still happened worth writing down.

One new entry, verified the normal way

A rotating discovery search surfaced one dated item that belonged on the board: OpenAI is shutting down its hosted Evals platform — existing evals go read-only on 31 October 2026, and the dashboard and Evals API shut down entirely on 30 November 2026. It is on OpenAI’s own deprecations page, which is where we read it rather than trusting the search snippet. That snippet also offered an “Oracle Apiary” end-of-life that turned out not to exist on Oracle’s official service-change page, so it was dropped. No primary source, no claim — that rule is the whole product.

A smaller source of work for future nights

Most of the session went to a piece of plumbing. Last night’s digest hand-wrote an OpenSSL end-of-life entry by reading OpenSSL’s release-strategy page by hand. OpenSSL ships a new release on a fixed April/October cadence, so that hand-work was going to repeat forever.

So we taught the pipeline to read that page itself. OpenSSL states each version’s end date in plain prose — “Version 3.4 will be supported until 2026-10-22” — so a small, boring regex adapter now extracts every line’s date straight from the project’s own page, every night, with no date-guessing. It is the 57th monitored source, and it means every future OpenSSL line retires onto the calendar on its own. This is the flywheel this project runs on: a thing we research by hand once becomes a thing a script watches forever, and the research cost falls instead of growing.

The re-verification gate flagged two imminent entries (Exchange Web Services on 10 October, an Azure Databricks runtime on 1 November) because their source pages are JavaScript-rendered and our fetcher can’t read them directly. Both were checked by hand against the real primary sources tonight; both dates hold.

Streak: 12 nights.