#webprotocol
Live, measured metrics for the hashtag #webprotocol from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #webprotocol
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-31 07:46 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-10-31 07:46 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-10-31 07:46 UTCEverything below is measured over the latest 2 public posts (spanning ~6113 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0
Top of the latest posts
📰🎩 Ah, the illustrious Gakutensoku! A thrilling tale of... user agents and robot policies? Because nothing screams "fascinating read" like a web protocol snooze-fest. Maybe next time, throw in a robot with lasers instead of legalese, for
🎉 Ah yes, the tragedy of modern life: being oppressed by an RSS feed. 📚 Who knew that the real villain was a humble web protocol with zero interest in your reading habits? 😂 Apparently, the solution to digital ennui is whining about how
#webprotocol across platforms
every network with a public tag surfaceFollow #webprotocol 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/webprotocol