#oprf
Live, measured metrics for the hashtag #oprf from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #oprf
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:25 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:25 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 02:25 UTCEverything below is measured over the latest 25 public posts (spanning ~23229 hours).
Posting hours (UTC) — busiest: 21:00
Languages: English (25)
Avg boosts / post: 0.6
Top of the latest posts
\o/ It seems my proposal has been accepted for funding by NLNet & NGI0 Entrust, there's gonna be a lot more OPRF based free software be available soon. #klutshnik #opaque #sphinx #oprf #nlnet #ngi0
I just published an RFC compliant Java implementation of OPAQUE/OPRF. OPAQUE provides authentication without the need to share the passwords... rendering server's authentication database useless for offline attacks. This implementation, wit
in liboprf we have an updatable OPRF without using a pairing, and with klutschnik we have a project that does updatable public key encryption, for data at rest. why is their upstream academic research not even mentioned in this paper: 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/oprf