#bsdtar
Live, measured metrics for the hashtag #bsdtar from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #bsdtar
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 19:59 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 19:59 UTCNo related tags with measured usage found for #bsdtar.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 19:59 UTCEverything below is measured over the latest 5 public posts (spanning ~21249 hours).
Posting hours (UTC)
Languages: English (4) · Polish (1)
Avg boosts / post: 0.6
Top of the latest posts
Dear #Linux Distributions, Please switch to #BSDTar by default. It's the archive Swiss Army Knife, able to read many, many additional file formats thanks to #libarchive. Thank you for coming to my TED talk, #WinningWithBSD
Przypadkowe narzekanie z krainy #Gentoo na dziś: 1. Testy w #LibArchive zaczęły się sypać (a #BSDCPIO oraz #BSDTar nagle zaczęły śmiecić wyjście), bo #LRZip postanowił zmienić przeznaczenie opcji `-q`. Przedtem wyłączała zupełnie szczegółow
Random #Gentoo moaning for today: 1. #LibArchive started failing its tests (and #BSDCPIO and #BSDTar started being verbose) because #LRZip decided to repurpose the `-q` option. Previously, it silenced all the verbose output it defaults to,
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/bsdtar