#blosc2
Live, measured metrics for the hashtag #blosc2 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #blosc2
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 08:34 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 08:34 UTCNo related tags with measured usage found for #blosc2.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 08:34 UTCEverything below is measured over the latest 31 public posts (spanning ~26089 hours).
Posting hours (UTC) — busiest: 12:00
Languages: English (31)
Avg boosts / post: 1.5
Top of the latest posts
Our @EuroSciPy 2025 tutorial on modern Blosc2 features is now online! 🚀 For the first time, we present our holistic view on how compression can revolutionize data handling, sharing, and computing. Learn how Blosc2 boosts performance for la
Just took the new engine in Python-Blosc2 4.0 for a spin, and the performance results are quite awesome. Processing a 400 MB array: 🔹 NumPy baseline: 146 ms 🔹 Blosc2 (on NumPy arrays): 73.1 ms (2x faster) 🔹 Blosc2 (on native Blosc2 array
🚀 We are thrilled to announce *TreeStore*, a new class in Python-Blosc2! It lets you give your datasets a hierarchical structure while keeping the speed and efficiency of `NDArray` instances. ⚡️ 📝 We've blogged all about it here: https://
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/blosc2