#cpio
Live, measured metrics for the hashtag #cpio from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #cpio
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 09:56 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 09:56 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 09:56 UTCEverything below is measured over the latest 10 public posts (spanning ~57702 hours).
Posting hours (UTC)
Languages: English (8) · German (1) · Russian (1)
Avg boosts / post: 0.2
Top of the latest posts
I got bored and reverse engineered how SCO #cpio is able to store such large files in their archives when the newc format only officially supports 4GiB file entries. I am not a coder, so I just made some files with cpio from the Heirloom To
Since 1993, I have favored #cpio archives for my personal data over #tar. When I used #Unix SYSVR3.2.3 on an AT&T 3B2/600, tar was buggy, and didn't preserve as much file details as cpio. I was archiving up some old backup incrementals for
https://astrid.tech/2026/03/28/0/linux-is-an-interpreter/ Amazing read! #linux #cpio #initrd #elf #interpreter
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/cpio