#fcli
Live, measured metrics for the hashtag #fcli from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #fcli
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 07:05 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 07:05 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 07:05 UTCEverything below is measured over the latest 17 public posts (spanning ~17111 hours).
Posting hours (UTC) — busiest: 20:00
Languages: English (17)
Avg boosts / post: 0
Top of the latest posts
Rewriting bits of #fcli in #C - makes a huge difference to not have to spin up a Python interpreter and import a load of libraries just to produce a tabular view of some relatively simple JSON. The whole experience is way more responsive.
I had been thinking about the filtering part of #fcli, my #Mastodon to #email bridge as 'similar to #procmail', but today I realised that if I add custom headers to the email messages it produces I can just use procmail itself. By interfaci
I'm thinking about experimenting with replacing the filters in #FCLI with something more general purpose, inspired by #procmail recipes. Procmail uses regular expressions on email headers (and bodies), so I wonder what the equivalent is for
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/fcli