#leveled
Live, measured metrics for the hashtag #leveled from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #leveled
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.online (Mastodon public tags API) · fetched 2026-07-28 20:35 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.online (Mastodon public search API) · fetched 2026-07-28 20:35 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-07-28 20:35 UTCEverything below is measured over the latest 3 public posts (spanning ~9896 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 1.3
Used together with
Top of the latest posts
A great description (in a Github issue) of Leveled's safety features. (by Leveled author Martin Sumner) https://github.com/martinsumner/leveled/issues/432 #Erlang #Leveled
Leveled is not a distributed key value store, but a backend for one (it is developed as a backend for Riak). In other words, if you want a *distributed* key value store, you need to integrate Leveled into your store implementation (as with
“What’s wrong with cookies?” “They’re hit and miss. I don’t trust a baked good that needs dunking in milk or coffee to add moisture. The moisture should be there.” “I won’t deny that moisture is essential to a quality cookie. Even different
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/leveled