#internetengineeringtaskforce
Live, measured metrics for the hashtag #internetengineeringtaskforce from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #internetengineeringtaskforce
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-09-29 21:09 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-09-29 21:09 UTCNo related tags with measured usage found for #internetengineeringtaskforce.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-09-29 21:09 UTCEverything below is measured over the latest 9 public posts (spanning ~55200 hours).
Posting hours (UTC)
Languages: English (7) · German (2)
Avg boosts / post: 1.1
Top of the latest posts
The #EFF (@eff) is right about the fear of system overloads caused by surging bot traffic: https://www.eff.org/deeplinks/2026/06/free-and-open-web-under-attack-ietf "However reasonable these fears may be, the answer is not to change the #IE
27th Birthday of #XMPP (formerly named #Jabber)! It is the date of #JeremieMiller announcement on #Slashdot! #OpenStandard #InstantMessaging #RealTimeText #CommunicationProtocol #IETF #InternetEngineeringTaskForce https://slashdot.org/story
Few days ago, it was the 26th Birthday of #Jabber/#XMPP! It is the date of #JeremieMiller announcement on #Slashdot! #OpenStandard #InstantMessaging #RealTimeText #CommunicationProtocol #IETF #InternetEngineeringTaskForce https://slashdot.o
#internetengineeringtaskforce across platforms
every network with a public tag surfaceFollow #internetengineeringtaskforce 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/internetengineeringtaskforce