#okvs
Live, measured metrics for the hashtag #okvs from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #okvs
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-09-01 15:50 UTC1 uses by 1 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-09-01 15:50 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-09-01 15:50 UTCEverything below is measured over the latest 5 public posts (spanning ~48023 hours).
Posting hours (UTC)
Languages: English (4) · French (1)
Avg boosts / post: 0
Top of the latest posts
RE: https://functional.cafe/@aziz/117160401355122531 Fixed #okvs vs #databases world
AFAIK, the most advanced #async #okvs #database is sled written with #rust ref: https://docs.rs/sled/latest/sled/
It may be possible to cross the single-writer limitation with #okvs layered on top of #sqlite and SQLite LSM extension (that is already an okvs); without loosing ACID guarantees. Disclaimer: In most cases, the single writer limitation of SQ
#okvs across platforms
every network with a public tag surfaceFollow #okvs 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/okvs