#Fermyon
Live, measured metrics for the hashtag #Fermyon from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #fermyon
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 19:17 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 19:17 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 19:17 UTCEverything below is measured over the latest 21 public posts (spanning ~23576 hours).
Posting hours (UTC) — busiest: 00:00
Languages: English (21)
Avg boosts / post: 0.6
Top of the latest posts
Joel Dice of #Fermyon has written a great early look at #webassembly components preview 3 here: https://www.fermyon.com/blog/looking-ahead-to-wasip3. I very much appreciate the contributor list at the bottom of the post, as it indicates how
Hey, here's the strangest thing: I was just using #Fermyon's #spin to host a #tinygo wasm preview 2 component and it "just worked" in Spin 2.0.1: squillace@idiopath:~$ hey -n 2000 -c 5 http://127.0.0.1:3000 Summary: Total: 0.4292 secs Slowe
Passkeys? In Crux? With #Fermyon Spin? Can it get any more cutting edge?? Awesome work by @stuartharris, and a great example of nesting Crux apps Check out https://github.com/StuartHarris/crux-passkey
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/fermyon