#diskcache
Live, measured metrics for the hashtag #diskcache from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #diskcache
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 22:46 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 22:46 UTCNo related tags with measured usage found for #diskcache.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 22:46 UTCEverything below is measured over the latest 3 public posts (spanning ~27044 hours).
Posting hours (UTC)
Languages: English (2) · French (1)
Avg boosts / post: 0.3
Top of the latest posts
I've only just discovered #DiskCache memoization for #Python. It's a nice little persistent #cache that lets you re-run a Python script without needing to re-run things you've already calculated. Kind of like a super lightweight version of
I'm so excited; it took me roughly 5 years to get to a working solution, struggling through #redis, #nameko, #diskcache (and a slew of others) in my #python #microservices environment. Solved using a centralized #postgres database, which au
la bibliothèque #diskcache est intéressante pour plusieurs raisons (https://github.com/grantjenks/python-diskcache) : - écrite en pur #Python - persistance du cache sur disque avec #SQLite - fonctionnalités avancées, comme locking (cf. http
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/diskcache