#fedify
Live, measured metrics for the hashtag #fedify from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #fedify
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 04:27 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-27 04:27 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 04:27 UTCEverything below is measured over the latest 40 public posts (spanning ~3223 hours).
Posting hours (UTC) — busiest: 04:00
Languages: English (27) · Chinese (1)
Avg boosts / post: 7
Top of the latest posts
If you'd like to preview the #tutorial I'm writing on building a small federated image sharing service, similar to @pixelfed, with @fedify and @nuxt, here it is: https://pr-731-0.fedify.pages.dev/tutorial/content-sharing If you'd like to gi
Naru, the Korean version of #Neocities, reportedly added an #ActivityPub implementation in just an hour using #Fedify. If you also want to implement ActivityPub quickly, give Fedify a try! https://hackers.pub/@jihyeok/019da3d9-45b8-7629-96a
Honestly, I don't really care what strategy other #ActivityPub implementations follow to comply with the spec. (I solved it in #Fedify by just using a proper JSON-LD processor.) It's just a bit annoying that I always send valid JSON-LD docu
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/fedify