#bzip2
Live, measured metrics for the hashtag #bzip2 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #bzip2
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 07:08 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 07:08 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 07:08 UTCEverything below is measured over the latest 40 public posts (spanning ~7570 hours).
Posting hours (UTC) — busiest: 16:00
Languages: English (30) · German (5) · Chinese (Taiwan) (3) · Japanese (1) · Russian (1)
Avg boosts / post: 0.5
Top of the latest posts
WARNING TIL that bunzip2 in Linux / Debian / MX Linux deletes, I repeat, DELETES the original archive when you run it in vanilla form `bunzip2 dfly-x86_64-6.4.2_REL.iso.bz2` resulted in the iso being unpacked with deletion of the original W
For fun I implemented lbzip2's lbzcat (parallel bzip2 decompression) clone in rust, using the bzip2 crate. I found a lot of different interesting things. 1/N #lbzip2 #bzip2 #RustLang
@BRicker @Boston_PM my favourite C portability screw up is #bzip2 which insists that `short` be 16 bits. Getting that to work on a platform where short, int and long were all 64 bits, and where you only had C89, no fancy C99 data types like
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/bzip2