#templ
Live, measured metrics for the hashtag #templ from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #templ
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-28 03:31 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-28 03:31 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 03:31 UTCEverything below is measured over the latest 25 public posts (spanning ~21957 hours).
Posting hours (UTC) — busiest: 16:00
Languages: English (21) · French (3) · Dutch (1)
Avg boosts / post: 0.2
Top of the latest posts
@loop0 Lately, I'm most comfortable with #Go + #Templ + #HTMX (GoTH). Since the standard library's ServeMux gained support for HTTP methods I see no need for external routers. Middleware I simply write myself, after all, it's just a functio
I must say #golang and #templ, are like catnip. 😅 You can do SO much with those two. Case in point, #irgo. A new framework for targeting mobile and desktop apps. All with go, templ, and #datastar. 🫡 https://irgo.dev/
I'm in an internal struggle with building things now. Do I either use #golang, #nats, #htmx, #templ, #postgres, #riverqueue, and bask in the greatness of fitting each to perfection? 🤔 Or do I use #elixir, #phoenix, #postgres, #oban, and fi
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/templ