#tomo
Live, measured metrics for the hashtag #tomo from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #tomo
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-27 08:49 UTC1 uses by 1 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-27 08:49 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 08:49 UTCEverything below is measured over the latest 40 public posts (spanning ~13580 hours).
Posting hours (UTC) — busiest: 18:00
Languages: English (34) · Ukrainian (3)
Avg boosts / post: 0.9
Top of the latest posts
blog post: death's inheritance and the future of tomo today, tomo appears to be the only fork of the RSLight nntp server that is still alive. so what now? i'll be honest: once Thom/Retro Guy died, i was very tempted to trash the project and
fuck it. i'm declaring project bankruptcy with rslight-tomo. 😆 😭 after futzing around with tomo's (rslight-based) code for the afternoon, i realized that it's such an ensnarled mess that it's not worth trying to untangle the old rslight c
new tomo dev .plan update tomo is dead: long live tomo a month away from tomo gave me time to think about why the project stalled out for such a long time, and where it could go now. tldr: tomo is getting a reboot as shard-based federated d
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/tomo