#Emmett
Live, measured metrics for the hashtag #Emmett from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #emmett
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-09-25 17:10 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-09-25 17:10 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-09-25 17:10 UTCEverything below is measured over the latest 40 public posts (spanning ~14818 hours).
Posting hours (UTC) — busiest: 11:00
Languages: English (40)
Avg boosts / post: 0.9
Top of the latest posts
⚠️ Emmett framework (2.5.0 – <2.8.1) suffers from a CRITICAL path traversal (CVE-2026-39847). Attackers can remotely read files outside the asset directory. Patch by upgrading to 2.8.1+. Details: https://radar.offseq.com/threat/cve-2026-398
@Aaron_David Next: bunk sofa, brought to by #Emmett
What compilers have to do with event-driven pipelines? At first glance? Nothing! But after thinking about the new design in #Emmett, I changed my mind! I wrote today on #ArchitectureWeekly on how building an Event-Driven pipeline led me to
#emmett across platforms
every network with a public tag surfaceFollow #emmett 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/emmett