#libsodium
Live, measured metrics for the hashtag #libsodium from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #libsodium
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 · mas.to (Mastodon public tags API) · fetched 2026-07-27 20:10 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-07-27 20:10 UTCNo related tags with measured usage found for #libsodium.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-07-27 20:10 UTCEverything below is measured over the latest 17 public posts (spanning ~46386 hours).
Posting hours (UTC) — busiest: 07:00
Languages: English (15)
Avg boosts / post: 2.2
Top of the latest posts
https://codeberg.org/pkw/libs/src/branch/main/crypt/crypt.c I'm adding basic secret key handling to my "batteries included" C repo. It's libsodium. This is because I want to encrypt and recover secrets that I'll put into cookies and the lik
Communication from the #Haskell Cryptography Group: "A vulnerability in #libsodium 's validation of ed25519 elliptic curve points: You are likely not affected" https://haskell-cryptography.org/blog/libsodium-vulnerability-ed25519-valid-poin
A Vulnerability in Libsodium https://00f.net/2025/12/30/libsodium-vulnerability/ #HackerNews #Libsodium #Vulnerability #Security #Cybersecurity #OpenSource #TechNews
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/libsodium