#excusion
Live, measured metrics for the hashtag #excusion from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #excusion
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 11:56 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 11:56 UTCNo related tags with measured usage found for #excusion.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 11:56 UTCEverything below is measured over the latest 3 public posts (spanning ~34348 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 2.7
Top of the latest posts
🇫🇷 🇬🇧 🇪🇸 🇫🇷 Lors de ma randonnée de septembre sur le tour des volcans d’Auvergne (France). 113 km 6 jours, La distance et la durée ne permet pas de voir toute la beauté de cette région, mais déjà un bel aperçu. 🇬🇧 During my Septem
@wim_v12e I've mentioned the website mechanism in an earlier HN post: https://news.ycombinator.com/item?id=27410503 The though first occurred to me in the context of Ling's Cars and its ... exhuberant ... design ethic: https://ello.co/dredm
@wim_v12e In thinking through possible validations for the metaverse, an earlier realisation emerges again. I've previously argued that large, bloated, slow websites requiring highly-provisioned systems and high bandwidth are a market-segme
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/excusion