#fedicache
Live, measured metrics for the hashtag #fedicache from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #fedicache
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 00:22 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 00:22 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 00:22 UTCEverything below is measured over the latest 7 public posts (spanning ~5730 hours).
Posting hours (UTC)
Languages: English (7)
Avg boosts / post: 1.3
Top of the latest posts
1/ RE: https://mastodon.social/@reiver/114019537398771505 The number one cause of Fediverse servers crashing seems to be the storage drives filling up with cached Fediverse user data — posts, profiles, avatar images, header images, etc. But
I tried figuring out why the Desk Chair Analysts site was briefly spiking after sharing an article on ActivityPub. I thought I implemented the #FediCache properly on the server, but it doesn't behave in the same way MajorLinux.com does. Wel
2/ Misskey and the Misskey forks (ex: Firefish, Sharkey, etc) seem to also be prone to their storage drives filling with: • logs • npm cache • yarn cache #DeSo #FediAdmin #FediCache #FediDev #FediDevs #Fediverse #Firefish #FirefishAdmin #Mi
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/fedicache