#RFC3339
Live, measured metrics for the hashtag #RFC3339 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #rfc3339
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-29 00:18 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-29 00:18 UTCNo related tags with measured usage found for #rfc3339.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 00:18 UTCEverything below is measured over the latest 21 public posts (spanning ~34060 hours).
Posting hours (UTC) — busiest: 06:00
Languages: English (19) · Dutch (1) · French (1)
Avg boosts / post: 1
Top of the latest posts
@tykling but #ISO8601 has so many nice things that aren't in #RFC3339 /o\ https://ijmacd.github.io/rfc3339-iso8601/
So this is cool: https://ijmacd.github.io/rfc3339-iso8601/ RFC 3339 is of course the best, since it supports date/time with space in between: 2024-12-12 16:03:17 #RFC3339 #ISO8601
@whreq Good point! Using a space instead of a 'T' is easier to read. I've been an ISO 8601 fan for decades, but now I'm fully onboard with RFC 3339. #RFC3339 #iso8601
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/rfc3339