#jsonld
Live, measured metrics for the hashtag #jsonld from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #jsonld
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:51 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:51 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 02:51 UTCEverything below is measured over the latest 40 public posts (spanning ~3613 hours).
Posting hours (UTC) — busiest: 18:00
Languages: English (32) · Russian (5) · German (2) · American English (1)
Avg boosts / post: 2
Top of the latest posts
In ActivityPub, these are all equivalent: "type":"Banana" "type":["Banana"] "type":{"＠id":"Banana"} "type":[{"＠id":"Banana"}] "type":{"id":"Banana"} "type":[{"id":"Banana"}] "＠type":"Banana" "＠type":["Banana"] "＠type":{"＠id":"Banana"} "＠typ
Just had to add a workaround to #Fedify for http://joinmastodon.org/ns, a JSON-LD context URL that has never actually served a JSON-LD document. Mastodon has always inlined the term definitions, but some implementations put it as a bare URL
This is from the JSON-LD spec. ActivityPub / ActivityStream are based on JSON-LD. I think it was a very bad idea for JSON-LD to define "number" this way! It makes it so numbers with fractional values are inexact & lossy. This include values
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/jsonld