#sha256
Live, measured metrics for the hashtag #sha256 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #sha256
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 11: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 · fosstodon.org (Mastodon public search API) · fetched 2026-07-27 11:25 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 11:25 UTCEverything below is measured over the latest 40 public posts (spanning ~15470 hours).
Posting hours (UTC) — busiest: 19:00
Languages: English (29) · Russian (7) · Spanish (2) · Swedish (1)
Avg boosts / post: 0.3
Top of the latest posts
Thanks to @Monorepo for doing most of this, which needed changes to both the release process and the website: releases since 13th January now show SHA-256 checksums instead of MD5! https://www.python.org/downloads/release/python-3150a4/ #Py
My #2026 resolution was field-testing sha256 git repos and I converted one of my minor projects, but since Github only supports sha1 I've moved the repository to codeberg: https://codeberg.org/kpcyrd/ssh-keyonly Everything else worked well.
1/2 Exciting news: we just published a new paper: "Preimage attacks on round-reduced MD5, SHA-1, and SHA-256 using parameterized SAT solver", by Oleg Zaikin If you are interested in security, cryptology, or Constraint Programming, definitel
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/sha256