#ietf123
Live, measured metrics for the hashtag #ietf123 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #ietf123
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 04:07 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 04:07 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 04:07 UTCEverything below is measured over the latest 40 public posts (spanning ~1045 hours).
Posting hours (UTC) — busiest: 10:00
Languages: English (34) · French (5) · German (1)
Avg boosts / post: 1.2
Top of the latest posts
I’m on my way back from #IETF123 in Madrid. Here is a quick summary: · A seven day conference is pretty exhausting 😪 · Pretty excited about the long term future of #MLS. Not necessarily for interoperability but as a well tested building bl
That was quite the week at #IETF123, with contributions to the hackathon, NomCom, the @internetsociety Policymaker program, and the @ietf_wg_dnsop and GROW working groups, in various roles between the @nlnetlabs crew. But I think I'm most e
In Memoriam: Dave Täht @mtaht - Jason Livingood at @ietf 123 Plenary 🖤 Very much appreciated! Watch it here: https://youtu.be/5Ju82sykvhM?si=uUGvYQ3W0W8MsXPJ #IETF123 #IETF #bufferbloat #RFC8290 #FQ_CoDel #sch_CAKE #LibreQoS #QoE #OpenSour
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/ietf123