#e_id
Live, measured metrics for the hashtag #e_id from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #e_id
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-28 01:46 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-28 01:46 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 01:46 UTCEverything below is measured over the latest 9 public posts (spanning ~60911 hours).
Posting hours (UTC)
Languages: English (5) · German (2) · French (2)
Avg boosts / post: 0.9
Top of the latest posts
@diekenbrock @lagedernation Elster habe ich nocht ausprobiert. Ich habs mich mit der #e_id (digitaler Perso) ausgewiesen, musste in dem Prozess aber noch eine #BundID anlegen. Das hat alles aber ohne Probleme funktioniert 🧐
#e_id #ZKP This just blew my head: we're looking at the latest and greatest ZKP frameworks before digging more into noir, and I saw this: https://doc.rust-lang.org/rustc/platform-support/riscv32im-risc0-zkvm-elf.html A freakin' RUST TARGET
#E_ID #ZKP Having some fun with Noir and ZKPs to prove the knowledge of ECDSA: https://github.com/eid-privacy/noir-playground-ineiti We're doing this in order to understand how good nowadays ZKP libraries are in bringing understandable and
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/e_id