#ccache
Live, measured metrics for the hashtag #ccache from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #ccache
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:03 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:03 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 11:03 UTCEverything below is measured over the latest 16 public posts (spanning ~58546 hours).
Posting hours (UTC) — busiest: 16:00
Languages: English (15) · German (1)
Avg boosts / post: 0.3
Top of the latest posts
So I've wasted a lot of time testing the new #LLVM snapshot yesterday, then spent some time debugging why I have almost no #ccache hits on the second rebuild… only to discover /var/cache/ccache ran out of space. I suppose it's enterprise-gr
I recently discovered gitcache, it's like ccache, but for git clone: https://github.com/seeraven/gitcache I periodically need to do a full clean + rebuild of some cmake projects that download and build their dependencies, and gitcache speed
#ccache sure creates a lot of files! I accidentally had #rsync back it up (as part of /var) before a #freebsd OS upgrade.
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/ccache