#keyserver
Live, measured metrics for the hashtag #keyserver from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #keyserver
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 · mastodon.social (Mastodon public tags API) · fetched 2026-09-13 23:11 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-09-13 23:11 UTCLive pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-09-13 23:11 UTCEverything below is measured over the latest 40 public posts (spanning ~54634 hours).
Posting hours (UTC) — busiest: 11:00
Languages: English (31) · German (4) · Spanish (2) · Danish (1)
Avg boosts / post: 3.3
Top of the latest posts
We are pleased to announce the release of Hockeypuck 2.3. Hockeypuck 2.3 is primarily a technical-debt release, but also adds features to ease the upgrade process in a production environment: * Updates to the PostgreSQL table schemas * Offl
News from the coalface! The pgpkeys.eu test swarm is now running an alpha version of #hockeypuck 2.3, and is gradually reindexing itself to populate the new SQL table structure required for RFC9580 and PQC support. The PostgreSQL storage la
We are pleased to announce the release of Hockeypuck 2.3.2. Hockeypuck 2.3.2 is primarily a bugfix release to revert a cryptographic policy default in go 1.24 that rendered some historical keys unverifiable. It also fixes some papercuts in
#keyserver across platforms
every network with a public tag surfaceFollow #keyserver straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/keyserver