#blockstorage
Live, measured metrics for the hashtag #blockstorage from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #blockstorage
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-11-12 11:47 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-11-12 11:47 UTCNo related tags with measured usage found for #blockstorage.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-11-12 11:47 UTCEverything below is measured over the latest 24 public posts (spanning ~62854 hours).
Posting hours (UTC) — busiest: 12:00
Languages: English (17) · German (3) · Japanese (2) · Swedish (1)
Avg boosts / post: 1.4
Top of the latest posts
Probably the most interesting new feature in Proxmox 9 (Beta 1): Finally we're able to create #Snapshots of VMs with shared block storage (such like #iSCSI, #FibreChannel & #NVMeoF) with LVM Thick without doing dirty workarounds. Well done
I don't know if anybody noticed #ZeroFS yet, but it seems there is a completely user space-implementation of #NFS and #blockstorage on top of #S3 #objectstorage: https://github.com/Barre/zerofs Including a demo running #ZFS on top of it whi
#ReleaseWednesday Just pushed a new version of https://thi.ng/block-fs, now with additional multi-command CLI tooling to convert & bundle a local file system tree into a single block-based binary blob (e.g. for bundling assets, or distribut
#blockstorage across platforms
every network with a public tag surfaceFollow #blockstorage straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/blockstorage