#fzx
Live, measured metrics for the hashtag #fzx from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #fzx
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:17 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 08:17 UTCNo related tags with measured usage found for #fzx.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 08:17 UTCEverything below is measured over the latest 6 public posts (spanning ~584 hours).
Posting hours (UTC)
Languages: English (6)
Avg boosts / post: 0.3
Top of the latest posts
What an I waiting for? Can I start tonight? I guess I’ve started already (I’ve already begun to experiment with hosting #htmx on experimental builds of #fzx) but maybe I can start re-writing jasongullickson.com in htmx right now? 🤔🤔🤔
The path here is to move everything to #htmx & #hyperscript running on #fzx (this will incorporate/depreciate my work on #ApresWeb) I have a lot to say about why, but its way too much to write in this little box.
But if it does make sense, and if I can come up with a reasonable way to integrate it, this would finally answer two question that have been holding back a lot of work on #fzx and perhaps more important open a wide-range of new applications
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/fzx