#microdon
Live, measured metrics for the hashtag #microdon from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #microdon
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 05:34 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-27 05:34 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 05:34 UTCEverything below is measured over the latest 6 public posts (spanning ~12877 hours).
Posting hours (UTC)
Languages: English (6)
Avg boosts / post: 0.8
Used together with
Top of the latest posts
I started working on the #Microdon Fediverse back-end again because (in part) I wanted to work on the #ProToGo Fediverse front-end again. Microdon is a light-weight single-user Fediverse back0end. ProToGo is a career oriented Fediverse fron
RE: https://mastodon.social/@reiver/112921051726027193 2/ I want this (back-end Fediverse servers and front-end Fediverse clients as separate projects) for myself, too. To try to make development for myself easier. One of the Fediverse serv
RE: https://mastodon.social/@reiver/112921051726027193 1/ The Fediverse would be better off if if back-end servers and front-end clients were separate projects. I have been arguing that for a while. (I know I am not the only one.) With resp
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/microdon