#linstor
Live, measured metrics for the hashtag #linstor from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #linstor
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 22: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-27 22:56 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 22:56 UTCEverything below is measured over the latest 20 public posts (spanning ~48754 hours).
Posting hours (UTC) — busiest: 15:00
Languages: English (11) · Russian (6) · French (2) · Danish (1)
Avg boosts / post: 0.4
Top of the latest posts
I'm not sure how this happened but it did. I decided to give #linstor a try since I'm using #incus and it supports it as a back end. I now have a software defined block storage platform, distributed file system with #moosefs and using a vgw
I made more progress on my investigation. My previous tests were conducted with an LXC. I found, LXC migration needed to be restarted, which caused longer downtime I attempted to live migrate a VM with the same setup. The downtime was zero!
@vwbusguy have you looked at #linstor by #linbit? Pretty neat stuff
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/linstor