#pkcs11
Live, measured metrics for the hashtag #pkcs11 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #pkcs11
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-28 17:31 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-28 17:31 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 17:31 UTCEverything below is measured over the latest 30 public posts (spanning ~56029 hours).
Posting hours (UTC) — busiest: 09:00
Languages: English (16) · German (5) · Italian (3) · Russian (2) · Czech (1) · Swedish (1)
Avg boosts / post: 0.9
Top of the latest posts
While exploring use of PKCS #11 devices in #OpenPGP contexts, I stumbled over a bug (and potential security issue) in the yubihsm_pkcs11.so driver for #YubiHSM devices. Long form text by Christian Reitter (who walked me through the coordina
As the adoption of Delegated and Hybrid #RPKI grows, so are the number of Hardware Security Modules (HSMs) out in the field that people store Krill's key material on. #KMIP is pretty straight forward, but especially #PKCS11 can be quite fin
Over the last half year, I've spent time with PKCS #11 and PIV hardware security devices. In particular, using such devices in the #OpenPGP context. Entry points for results of this work: - https://codeberg.org/heiko/openpgp-pkcs11 - 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/pkcs11