#webcomponentcg
Live, measured metrics for the hashtag #webcomponentcg from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #webcomponentcg
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 22:27 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 22:27 UTCNo related tags with measured usage found for #webcomponentcg.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 22:27 UTCEverything below is measured over the latest 7 public posts (spanning ~25304 hours).
Posting hours (UTC)
Languages: English (7)
Avg boosts / post: 0.4
Top of the latest posts
@hawkticehurst @jaredwhite Glad to hear I am not the only one. My goal (too) is for it to on defined (or imported) once and used in each element that needs it. Let's push things in that direction in the spec'ing process!! 💪 My understandin
Let's use case the web forward! Who's with me? https://discord.gg/Q54dfmXtFU #webComponentCG #webComponents #shadowDOM #customElements #communityProtocols #w3c #wicg #html #css #js #andMore
@johannes some people like to think the #webComponentCG is this, but while there are definitely some over laps (make the browser do more, leverage the things it does, avoid including duplicates of those features, etc) it’s not _specifically
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/webcomponentcg