#WebStandards
Live, measured metrics for the hashtag #WebStandards from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #webstandards
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-27 04:28 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-27 04:28 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 04:28 UTCEverything below is measured over the latest 40 public posts (spanning ~975 hours).
Posting hours (UTC) — busiest: 09:00
Languages: English (39) · German (1)
Avg boosts / post: 3.1
Top of the latest posts
On the W3C blog: "CSS animations, human rights, and big accessibility at the AB Web Meetup" by @hdv Hidde noted that in early July the @ab held a F2F in Rotterdam 🇳🇱 and organized a get-together with the local developer community. This “W
Sharing this not because it’s about AI/LLMs but because it’s solid advice and the recommendations work equally well for *people* coding web applications (funny that, almost like these things were made by people for people or something). TL;
Did you know W3C has a YouTube channel? You can find talks from recent W3C events including: @xfq on "W3C China@20: Chinese layout requirements & W3C language enablement", @dontcallmeDOM on "Web Standards and AI-driven development" and @tor
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/webstandards