#fscache
Live, measured metrics for the hashtag #fscache from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #fscache
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 11:26 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-27 11:26 UTCNo related tags with measured usage found for #fscache.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 11:26 UTCEverything below is measured over the latest 3 public posts (spanning ~30278 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 0
Used together with
Top of the latest posts
No idea why, but the fscache daemon had died on my Plex machine at some point, so eventually it filled up with 650GB of NFS cache. 😅 It's fixed now, so I fired up an episode of Lego Masters I had half-watched at some point a while ago to m
#Linux Plumbers Conference and #Kernel Developments in #METRICFS , #FSCache , #HWMON http://www.tuxmachines.org/node/140683
#FSCache Rewritten But Even Its Developers Are Hesitant About Landing It For #Linux 5.9 https://www.phoronix.com/scan.php?page=news_item&px=FS-Cache-Rewrite-For-Linux-5.9
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/fscache