Tapping a link sent you to a diagram with everything greyed outTapping a link sent you to a diagram with everything greyed out
August 20, 2026 · Tapping a chip on a phone scrolled you to a diagram with every box dimmed and nothing lit, and the bot detector's cleanest evidence turned out not to exist.Tapping a link on my project pages sent you to a diagram with everything greyed out, and a check meant to spot robots kept flagging real people.
last updated
A “Touches:” chip under a feature on a project page is a link into the diagram below it: follow one and the page scrolls down and lights up the boxes that feature touches. What it was actually doing was landing you on a correctly scrolled diagram with every box faded to 0.22 and not one of them lit. On a phone that tap is the only path to the highlight there is, because there is no hover at all.
One click set off three things in the same tick, and two of them undid the first. The click lit the row. A focusout arrived in the same millisecond. macOS does not leave a clicked link focused, and that reads as focus leaving the row. Then a mouseleave 12ms later, at the exact coordinates the click was at: the fragment jump had scrolled the page from 1063 to 228 and taken the row out from under a pointer that never moved. The ticket only knew about the focusout, and both fixes it proposed leave the mouseleave standing.
So a click now pins the row, and the pin records where the pointer was. Those coordinates are the whole discriminator: a boundary event arriving at the pinned position means the row moved, one arriving anywhere else means the reader moved, and that second one must still clear or a click would leave the diagram lit for good. Deliberately not “has a mousemove happened since the click”, which is the obvious way to write it and is wrong: leaving a row in one fast flick delivers the mouseleave before the mousemove that caused it. The suite had been green through all of this, because a DOM stub has no scrolling in it and therefore no mouseleave to fire.
Elsewhere, the bot detector got a new scoring signal, sustained posting rate, for a reason worth stating: its strongest check needs three days of history, and the more prolific an account is, the less time one page of its comments covers. AutoModerator's reliable window is 297 items spanning 82 seconds. Volume was buying immunity from the check aimed at volume. A rate built from those 82 seconds is a ratio of two things genuinely observed; an hour-by-hour histogram built from them is measuring our own pagination.
Then the README claimed the gate sat in a clean gap: frozen humans top out at 0.92 an hour, the five known bots run 5.5 to 13,039. Two content-blind sweeps of 22 subreddits later, 23,000 comments and 16,264 authors with the top 48 scored for real, seven accounts fired the signal and six of them hand-read as unmistakably human. One of them posts reaction GIFs in r/Superstonk at 5.90 an hour, above RemindMeBot. The populations overlap, so no threshold separates them. The signal stays anyway, for a reason other than the one written down: it only ever pushes toward bot, it is floored and log-scaled and weighted 2 out of 15.5, so a person at 5.90 an hour earns 0.573 and still scores low. What protected those six was the signal's shape, not its gate's position.
One more, because I asked for it: the board was showing two jobs running while fourteen waited, the longest for nineteen minutes, across six different projects. The ceiling of two was set when nearly all work filed under one project, and that stopped being true. It is six now, one slot per busy project, and roles have lanes. Three audits of one checkout can run at once; two sessions that write to it still cannot.
Each project page has a drawing of how the thing is put together, and small labels above it saying which parts a feature touches. Tap one and the page should scroll down and light those parts up. It was doing the scrolling and none of the lighting. Everything went grey and stayed grey. On a computer you can hover instead. On a phone, the tap is the only way there is.
The tap was cancelling itself. Three things happen the instant you tap: the parts light up, the phone decides the link is no longer being touched, and the page scrolls, which slides the label out from under your finger. The last two both look like “the reader has moved on”, so they turned the lights back off a hundredth of a second after turning them on. It now remembers where your finger was when you tapped, which is enough to tell “the page moved” from “you moved”. My tests never caught it, because the fake page they run against cannot scroll.
The other thing: my Reddit bot detector got a new check for accounts that post relentlessly, hour after hour. My notes said it was safe, because the real people on file never went above one post an hour and the known robots ran from six to thirteen thousand. Rather than trust the note I went and looked at 23,000 recent comments from 16,000 people. Seven accounts tripped the check and six of them are plainly human. One posts reaction GIFs faster than a famous robot does. There is no safe gap between the two groups, and no setting would create one.
I kept the check anyway. It was never the cut-off protecting those six. The check can only nudge a verdict toward “robot”, it counts for very little on its own, and all six still came out clean. Right answer, wrong reason, which I would not have known without going to look.