#securitykeys
Live, measured metrics for the hashtag #securitykeys from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #securitykeys
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 02:24 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 02:24 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 02:24 UTCEverything below is measured over the latest 40 public posts (spanning ~28723 hours).
Posting hours (UTC) — busiest: 20:00
Languages: English (38) · German (2)
Avg boosts / post: 1.9
Top of the latest posts
Actually, you just significantly reduced my security, Gandi. You should have let the users manage this transition, or at least warn them ahead of time what was going to happen if they didn't. Replacing unphishable auth (old school U2F is st
So apparently, according to Yubico's CS, they accidentally placed a "normal", no-barcode Security Key into an "Enterprise Edition" packaging and told me not worry about it. They advised me to reset the key with ykman if I was still worried.
They're here! Not sure why I got the Enterprise Edition though... Seems the only difference is a bar code on the backside compared to having nothing on the normal version. #yubikey #yubikeys #yubico #CyberSecurity #OnlineSecurity #securityk
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/securitykeys