#hotwirejs
Live, measured metrics for the hashtag #hotwirejs from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #hotwirejs
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-09-30 05:14 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-09-30 05:14 UTCNo related tags with measured usage found for #hotwirejs.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-09-30 05:14 UTCEverything below is measured over the latest 2 public posts (spanning ~1366 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0
Top of the latest posts
@jofr @ajb the slow argument does generally not work anymore. Since ages. And since you migrated to Python it's useless to even bring it up here, since you didn't migrate to a faster platform, didn't you? 😉 Library-wise it's a smaller sele
@mbajur my problem is that the #Rails ecosystem already has a lot of simple #CMS. #AlchemyCMS has features that my customers know from other professional CMS and therefore expect them to be included as well. However, a #hotwire revamp for #
#hotwirejs across platforms
every network with a public tag surfaceFollow #hotwirejs 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/hotwirejs