#ietf
Live, measured metrics for the hashtag #ietf from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #ietf
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-07-27 07:00 UTC18 uses by 17 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-07-27 07:00 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-07-27 07:00 UTCEverything below is measured over the latest 40 public posts (spanning ~291 hours).
Posting hours (UTC) — busiest: 07:00
Languages: English (29) · German (6) · French (3) · Dutch (1)
Avg boosts / post: 2.5
Top of the latest posts
During the @ietf #hackaton we worked with @dino and @daniel from Conversations on the XEP-0490: Message Displayed Synchronization synchronization implementation ✨ This means if you read a message on a device it's shown as read on all the ot
With over 100 active Internet Drafts on various topics around AI, a third of the available side meetings, and nearly half of the HotRFC lightning talks at #IETF 126, I’m feeling more than a little overwhelmed with all the heat and so very l
Opened a ticket at @videolan about the issue of selecting the wrong interface for #multicast: https://code.videolan.org/videolan/vlc/-/work_items/29992 It's basically the same issue I had also reported for #Qaul / #libp2p: https://github.co
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/ietf