#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.

hashtag.org network · sponsored

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.

$2,449.80/ year · 4-character #name
Claim #oprf — $2,449.80/yr→Buy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
22
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 22
0
Avg reactions / post
Mastodon · last 22
—
Reddit posts / month
Reddit search
—
Open-web mentions
hashtag.org Firehose

Day-by-day usage

measured · mastodon.online (Mastodon public tags API) · fetched 2026-10-14 12:19 UTC
0
10-08
0
10-09
0
10-10
0
10-11
0
10-12
0
10-13
0
10-14

0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.

Related hashtags

measured · mastodon.online (Mastodon public search API) · fetched 2026-10-14 12:19 UTC
#OPRFHS
0 uses · 0 accounts / 7d
#oprfs
0 uses · 0 accounts / 7d
#oprfhighschool
0 uses · 0 accounts / 7d
#oprfflagfootball
0 uses · 0 accounts / 7d
#oprfbaseballteam
0 uses · 0 accounts / 7d

Live pulse

measured · mastodon.online (Mastodon tag timeline) · fetched 2026-10-14 12:19 UTC

Everything below is measured over the latest 22 public posts (spanning ~22656 hours).

Posting hours (UTC) — busiest: 21:00

00:0012:0023:00

Languages: English (22)

Avg boosts / post: 0.5

Top of the latest posts

  • 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

    CodeHead :emacs:@[email protected]♥ 0↻ 02026-02-28 21:21 UTCView post →

  • 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

    stf@[email protected]♥ 0↻ 02025-02-07 15:31 UTCView post →

  • evolution of generative password "storage" over the last decades: 1. "password" 2. hash("password") 3. hmac("password", site) 4. oprf("password"+site, sphinx-oracle) 5. t-oprf(password+site, [sphinx-oracle1, sphinx-oracle2, ... sphinx-oracl

    stf@[email protected]♥ 0↻ 12025-01-13 21:40 UTCView post →

#oprf across platforms

every network with a public tag surface

Follow #oprf 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.

X (Twitter) ↗Instagram ↗TikTok ↗Facebook ↗LinkedIn ↗YouTube ↗Threads ↗Bluesky ↗Mastodon ↗Reddit ↗Pinterest ↗Tumblr ↗

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