#datahoarding
Live, measured metrics for the hashtag #datahoarding from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #datahoarding
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 05:18 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 05:18 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 05:18 UTCEverything below is measured over the latest 40 public posts (spanning ~10473 hours).
Posting hours (UTC) — busiest: 16:00
Languages: English (39) · German (1)
Avg boosts / post: 0.9
Top of the latest posts
3-2-1-1-1 Backup Rule (Apocalypse Edition) 3 Backups 2 Different media 1 Offsite backup 1 Backup in an Arctic vault 1 Extra-planetary backup Because if your data doesn't survive a meteor strike, did you even have a backup strategy? #SysAdmi
So, all this #DataHoarding I've been up to has me wondering: Are tape backups still a thing? Like, if you want to store a petabyte or so of data and you don't care about random access, it seems like that'd be an economical way to do it. Or
I’m considering a used Synology DS916+ 4‑Bay NAS with 4x 12 TB Seagate Exos X12 drives. I've heard that this model isn’t the most reliable, but the plan is to replace the drives one by one over time. Building such a setup from scratch would
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/datahoarding