#Wazero
Live, measured metrics for the hashtag #Wazero from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #wazero
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-29 23:11 UTC1 uses by 1 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-29 23:11 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 23:11 UTCEverything below is measured over the latest 40 public posts (spanning ~29146 hours).
Posting hours (UTC) — busiest: 08:00
Languages: English (36) · Italian (3) · Russian (1)
Avg boosts / post: 0.7
Top of the latest posts
So I needed a WebP encoder for a Go project where I had #CGO disabled. I found there is an option using #libwebp compiled to #wasm running on #wazero, but that's pretty slow and uses lots of memory. So I made a pure #GoLang encoder, ported
Another thing to be proud of: the tail spec has been merged into the #wazero #wasm runtime. Even though it's relatively simple, it actually took a few weeks to get right in the interpreter and in both backends (arm64 and amd64). Thanks @ncr
me, explaining #dwarf entries in #wazero and #wzprof Yes, I just put these on my slides. #go #golang
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/wazero