Two filters had been dropping work with nothing logging itTwo hidden checks were quietly throwing work away
August 2, 2026 · Neither failure logged anything. One left three tasks stuck forever; the other ignored every issue without a particular label. Both are now fixed and visible.Two problems were quietly losing work with nothing showing that anything was wrong. Both are fixed, and the site now explains its own jargon.
last updated
Two filters, both silent
The day started with a task that had gone quiet, and the cause had nothing to do with the channel it came in on. A concurrency guard caps one running task per issue, which is sensible, but three rows had been left marked running by sessions that died, so those issues could never dispatch again. Nothing logged it. Replies simply stopped, and somebody eventually noticed.
A second, unrelated filter turned up the same day: the webhook only ever dispatched an issue carrying a particular label, added early as a safety measure and never revisited. Every issue without it was received, acknowledged, and dropped, which from the outside is indistinguishable from a webhook that was never delivered.
The theme is the same one twice. Both failures were survivable; what made them expensive is that neither said anything. The stuck rows had been patched by hand once before, which is a fix that lasts exactly until the next time.
A glossary, and a Technical/Simple toggle
The site now holds a glossary of its own jargon across five categories, and (the more useful half) every post and project auto-links the first plain-text mention of any glossary term to its entry. Nothing has to be marked up by hand, so the linking cannot fall behind the writing.
Alongside it, every page now carries a plain-language version of itself and a toggle in the header that swaps the whole site between them. The simple version is a shorter account rather than a translation, because a jargon-free paragraph of the same length is usually still unreadable.
An SSH account that can only read a log
Closing out the day: a second, deliberately low-privilege account whose only possible action from anywhere is to tail one log file. Worth a second look before shipping. A plain reading of the address restriction suggests it denies everything outside the private network, but checking the actual behaviour showed the rule is more subtle than it reads.
Two problems, both silent
A task had gone quiet, and the reason turned out to be a safety check working too well: three jobs had been left marked as still running by sessions that died, so those tasks could never start again. Nothing anywhere said so. Replies just stopped.
A second, unrelated problem surfaced the same day: an early safety filter meant only specially marked work was ever picked up. Everything else was received, accepted, and quietly thrown away, which looks exactly like nothing ever arriving.
Both were survivable. What made them expensive is that neither said anything was wrong.
A glossary, and plain English everywhere
The site now explains its own jargon, and links any technical term to its explanation automatically the first time it appears, so the explanations cannot fall behind the writing.
Every page also has a plain-language version now, with a switch at the top. The simple version is a shorter account rather than a word-for-word translation, because removing the jargon alone rarely makes something readable.