#webvtt
Live, measured metrics for the hashtag #webvtt from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #webvtt
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 23:06 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 23:06 UTCNo related tags with measured usage found for #webvtt.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 23:06 UTCEverything below is measured over the latest 16 public posts (spanning ~60501 hours).
Posting hours (UTC) — busiest: 09:00
Languages: English (14) · French (2)
Avg boosts / post: 1.7
Top of the latest posts
The @w3c CSS #WorkingGroup publishes "Selectors Level 5' as #FPWD. The spec. extends Level 4, adding new #CSS selectors #timetogiveinput ▶️ https://www.w3.org/TR/selectors-5/ It introduces time dimensional pseudo-classes (':current', ':past
RE: https://mastodon.social/@firefoxwebdevs/116062636716280821 It is fantastic that one of the focus items for this year is #WebVTT. As a developer working for a bigger German TV network, I really struggle with that in browsers a lot. https
At iPres, a question I was asked about webvtt_metadata was "what happens if you mess up a line when you run it?" At the time, the best option was to correct the mistake in the csv and re-run the script - but that only works if you catch the
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/webvtt