#Passkey
Live, measured metrics for the hashtag #Passkey from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #passkey
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 00:33 UTC8 uses by 8 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 00:33 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 00:33 UTCEverything below is measured over the latest 40 public posts (spanning ~1237 hours).
Posting hours (UTC) — busiest: 20:00
Languages: English (23) · German (16) · Russian (1)
Avg boosts / post: 1.4
Top of the latest posts
I've come across a bit of #passkey fud over the years and some misconceptions. I've written a general overview of the topic and added a FAQ section at the bottom. I tried to keep the main part light on technical details with a few more tech
I am looking for a #passkey implementation on #linux which ideally integrates with [pass](https://www.passwordstore.org/) and stores its key material there. I have found [passless](https://github.com/pando85/passless) but I have doubts if t
#MagentaTV ist, wenn Du glaubst, komfortabel #passkey und Login über #Apple nutzen zu können und dann doch wieder durch X Reifen springen musst, um nen überflüssigen “Magenta” Account anzulegen, zwangsweise mit einer email und Telefonnummer
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/passkey