mootvelocity · follower velocity, not account age

For each account, mootvelocity pages backward through its own authored posts (skipping reposts) via the public AppView, newest first. The moment it finds two consecutive posts more than 60 days apart, that's a real silence — everything before it belongs to a separate, earlier era. The account's active since date is the oldest post in the streak that's still unbroken all the way to now. Velocity is followers ÷ active days × 30.44 — followers per month of that real active time, not per month since account creation. There's no cap on any of this: every moot (not just the first N found), every follow/follower page, and every account's full post history all get read in full — the scan only stops when it finds a real gap or runs out of history, so a big or high-frequency moot pool just takes longer instead of getting truncated into a bad number. Dimmer dots on the chart are estimates: a network hiccup cut a scan short before it could confirm a gap or reach the end of the account's history, so the streak may run further back than shown — velocity there is an upper bound, not exact. If that happens before even one 60-day window has been scanned, the window is too thin to mean anything, so that account falls back to its account-creation date instead of reporting a wild extrapolation (flagged "too dense to date" in the table). Accounts with zero original posts also fall back to their account creation date and are flagged as such. Idea and the "silent for over a year" framing came straight from @cee.wtf.