#BLAKE3
Live, measured metrics for the hashtag #BLAKE3 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #blake3
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:25 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:25 UTCNo related tags with measured usage found for #blake3.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-07-27 20:25 UTCEverything below is measured over the latest 15 public posts (spanning ~30472 hours).
Posting hours (UTC) — busiest: 13:00
Languages: English (15)
Avg boosts / post: 0.8
Top of the latest posts
The performance of blake3 multithreaded is very impressive: hmac-sha256 1.00 GB 0.327s <-- with hw accelerated sha256 blake2b-256 1.00 GB 0.952s <-- pure sw, used in borg 1.x blake3 1.00 GB 0.442s <-- pure sw, single-threaded blake3-mt 1.00
📦 Efficient file syncing for massive datasets? Forget classic rsync! ⚡ #BLAKE3 hashes instead of timestamps – hash 70GB in just ~20 seconds thanks to multithreading across all CPU cores #DevOps #Linux #SysAdmin #OpenSource #FileSync 📊 Alg
Maybe one day we will get Blake3 in hashlib #Python or not https://bugs.python.org/issue39298 The thread is full of insightful comments from power consumption, compilers, cpu, social interactions in the development of an open source languag
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/blake3