Journal
Reading silent users in session traces
I came to Controlpacketgrid able to plot uninstalls and unable to say what a quiet Tuesday meant. Our studio in Leamington had a healthy-looking D7 and a community channel that felt thinner each month. The dashboard was not broken. It was answering a louder question than the one that was costing us.
A silent user still produces a trace. They open on a commute, bounce a menu, background the process. If your session packet treats a hot-start from a notification as a return, you will count a pulse as loyalty. Module 03 of the flagship — which I sat as a visitor during Cartography — made us split wake-from-push from a chosen open. Overnight the “healthy” curve developed a valley. That valley had been there; we had paved it with a convenience property.
Reading silence is slower than reading a red tile. You pick a cohort that used to do a thing (a second match, a second order, a second journal entry) and you watch the week they stop choosing it while still technically present. The packets that remain are often accidental: a settings ping, a token refresh, a screen that loads because the OS restored state.
We now keep a relief map — their phrase, not ours — with the silent week drawn as a contour, not as a missing bar. Community still matters; it is not a substitute for grain. If you only have uninstalls in the board pack, you are narrating funerals and missing the people who already left the building with the lights on.