#fips
Live, measured metrics for the hashtag #fips from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #fips
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 · mas.to (Mastodon public tags API) · fetched 2026-10-14 08:10 UTC1 uses by 1 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-10-14 08:10 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-10-14 08:10 UTCEverything below is measured over the latest 40 public posts (spanning ~18218 hours).
Posting hours (UTC) — busiest: 15:00
Languages: English (27) · German (7) · French (1) · Chinese (1)
Avg boosts / post: 0.8
Top of the latest posts
@njsg The fun part of that is that a necessary pre-cursor would be going back to get ISO 8601:1988 ratified almost a decade earlier than it was in our universe. The sad part is that, conversely, in our universe ANSI X3.30-1971 and FIPS PUB
Does #FIPS (https://github.com/jmcorgan/fips) #mesh provide automatic connectivity for nodes behind symmetric CGNAT, or must one manually configure at least one reachable peer?
Happy death of #FIPS 140-2 day, everybody!
#fips across platforms
every network with a public tag surfaceFollow #fips straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/fips