#customelements
Live, measured metrics for the hashtag #customelements from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #customelements
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 · mastodon.online (Mastodon public tags API) · fetched 2026-07-27 12:20 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-07-27 12:20 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-07-27 12:20 UTCEverything below is measured over the latest 40 public posts (spanning ~13762 hours).
Posting hours (UTC) — busiest: 16:00
Languages: English (34) · German (1)
Avg boosts / post: 1.2
Top of the latest posts
In the last ~6 months someone linked to their blog about using JS-free custom elements for page structure and style in place of a methodology like BEM, e.g. using `<my-element>`/`my-element {}` instead of `<div class="my-element">`/`.my-ele
React-like syntax with WebComponents. After spending some time with Lit, I really appreciated its lightweight footprint but wasn't a fan of the class-based components. While Vue offers a great approach, I still prefer the intuitive nature
Custom Elements are cool but I wish there was also a controller mechanism where I do <span controller="foo bar"> in HTML and elementControllers.define("foo", FooClass) and get the same lifecycle hooks as custom element but also a attach and
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/customelements