#lbzip2
Live, measured metrics for the hashtag #lbzip2 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #lbzip2
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 · mastodon.social (Mastodon public tags API) · fetched 2026-07-27 20:05 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-07-27 20:05 UTCNo related tags with measured usage found for #lbzip2.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-07-27 20:05 UTCEverything below is measured over the latest 12 public posts (spanning ~46108 hours).
Posting hours (UTC) — busiest: 16:00
Languages: English (12)
Avg boosts / post: 0.7
Top of the latest posts
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
You'll find this benchmarking adventure in its own blog post "Performance lessons of implementing lbzcat in Rust" https://anisse.astier.eu/lbzip2-rs.html #RustLang #lbzip2 #bzip2 #benchmarking #performance
lbzip2 internally implements a full task-scheduling runtime, and splits tasks at a much smaller increments; it supports bit-aligned blocks (that are standard in bzip2 format), while my Rust implementation purposefully doesn't: I wanted to r
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/lbzip2