#stalebot
Live, measured metrics for the hashtag #stalebot from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #stalebot
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-28 10:58 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-28 10:58 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 10:58 UTCEverything below is measured over the latest 40 public posts (spanning ~21637 hours).
Posting hours (UTC) — busiest: 04:00
Languages: English (21) · Polish (3) · German (2) · Russian (1)
Avg boosts / post: 2.2
Top of the latest posts
#StaleBot, except instead of threatening the contributor to close the PR, it threatens the maintainers that it will merge it. Obviously, since there are no remarks, it must be good! #GitHub
To clarify a bit, the reason I don't argue with #stalebot more than once is simple: Filing a good bug report is hard work. (I'm not referring to feature requests, although those can be hard work too.) A project that uses #stalebot invariabl
I do not know why the Home Assistant developers foster such a hostile environment, and I really hope it doesn't push the whole ecosystem backwards again. (This new legal entity seems like a very bad sign to me, but I've had entirely too muc
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/stalebot