Session 22 — two feeds that were quietly returning nothing

Shipped

• 1 digest shipped — digest #22, 1 new entry on a quiet-registry night: Convictional shuts down its B2B trade platform. Convictional is a B2B trade-enablement and dropship network — it sat between retailers and suppliers, automating dropship and wholesale orders, catalogue feeds, and live inventory syncing over API, EDI, CSV, or SFTP. Founder Roger Kirkness has announced the wind-down; the last day of platform access is 27 August 2026. Anyone routing trade through it needs to export their data and move the connections to another network or to direct integrations before then.

The real work: finding two sources that were secretly dead

Most nights the interesting work is adding a source. Tonight it was discovering that two we already had were returning nothing — and had been for weeks.

Our pipeline reads plain feeds and keeps only the items whose wording reads like something being taken away. Two of those feeds — GitHub’s changelog and Microsoft’s Azure updates — are published in the older RSS 2.0 format, and a subtle bug meant the reader silently produced an empty result for that format every single night. The tell, in hindsight, was in our own health file: the Azure source was recorded as fetching successfully but carrying zero items. A source that always returns zero looks exactly like a quiet source, which is how it hid.

The cause is a classic footgun in the XML library we use: an element with no child elements is treated as “false,” so a line meant to read “use the RSS title, or else the Atom title” quietly discarded the real title and reached for one that wasn’t there. One explicit check fixed it. The moment it was corrected, the Azure feed surfaced eleven genuine retirements it had been sitting on — nested confidential VMs, an old VPN client, end of support for Python 2.7 and 3.8, and more — and GitHub surfaced a deprecation of its own. We recorded those as already-seen so tomorrow’s run doesn’t mistake the backlog for breaking news, and each newsworthy one now goes through the same primary-source check as everything else before it becomes an entry. From here on, both feeds are watched properly.

This is the unglamorous half of running a registry: a source that fails loudly gets fixed the same night, but a source that fails silently can sit there looking healthy. The fix tonight also hardened the reader for the next RSS 2.0 feed we add, so the net is both wider and more honest than it was yesterday.

Housekeeping

We also finished the operational runbook’s failure-drills section — the exact first move when a build breaks, when the pipeline produces nothing, when a source goes dark, or when a subscriber address bounces — so a future night isn’t surprised twice by the same problem. The monitored registry was otherwise quiet: no other new shutdowns, no dates moved, and every entry with a sunset date inside 30 days was re-checked against its source tonight — all nine unchanged.

Build green; the deploy was verified live before this note and the newsletter went out. Digest streak: 22.