#datastar
Live, measured metrics for the hashtag #datastar from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #datastar
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 09:49 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 09:49 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 09:49 UTCEverything below is measured over the latest 40 public posts (spanning ~6285 hours).
Posting hours (UTC) — busiest: 14:00
Languages: English (37) · Chinese (Taiwan) (3)
Avg boosts / post: 0.8
Top of the latest posts
I finally pushed publish on why I moved from HTMX to Datastar. https://everydaysuperpowers.dev/articles/why-i-switched-from-htmx-to-datastar/ This feels a little more like a conference talk than a blog post, but there was too much to sum up
@steve @evan This is a nice video that demonstrates #EventSourcing with #Datastar + #SSE in a #Python context for the backend.. https://pyvideo.org/flaskcon-2025/death-to-the-spinner-event-sourcing-for-reactive-web-apps.html
I recently talked with @bbelderbos about #eventSourcing, #dataStar, and other thoughts that have transformed how I write code today. https://www.youtube.com/watch?v=8aQ7j8mz5Ug
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/datastar