#rfc10001
Live, measured metrics for the hashtag #rfc10001 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #rfc10001
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-10-28 00:07 UTC1 uses by 1 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-10-28 00:07 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-10-28 00:07 UTCEverything below is measured over the latest 10 public posts (spanning ~1801 hours).
Posting hours (UTC)
Languages: English (9) · German (1)
Avg boosts / post: 1.6
Top of the latest posts
#Fastly already updated their nameservers to have AAAA records and are reachable via #IPv6 #RFC10001 🚀 Unfortunately they forgot to add glue records thus websites like @gnome or @fastlydevs @devs are still reported as not #IPv6ready with #
@equinox #RFC10001 #BCP91 not followed https://webres6.dev.sap/#report:6adf00a3-eaaafd16d50304c92430e092a413d33f1300bedfe0b3c1d1a883134d51f3e44c-4df0f311b550
@phils Yes totally agree and appreciate #webres6 For nameservers and resolvers we now have #RFC10001 by @tfiebig and co authors. Which should work without glue records. But I assume we all look towards the day where #RFC10001bis is ready an
#rfc10001 across platforms
every network with a public tag surfaceFollow #rfc10001 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/rfc10001