#jsonparse
Live, measured metrics for the hashtag #jsonparse from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #jsonparse
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.social (Mastodon public tags API) · fetched 2026-09-29 19:16 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.social (Mastodon public search API) · fetched 2026-09-29 19:16 UTCLive pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-09-29 19:16 UTCEverything below is measured over the latest 2 public posts (spanning ~336 hours).
Posting hours (UTC)
Languages: English (1) · German (1)
Avg boosts / post: 0.5
Used together with
Top of the latest posts
JavaScript's JSON.parse() has a second parameter: a reviver, used to transform data resurrected from the JSON string on the fly. In my case, I had a Map<string, Stuff> and serialized it to JSON of the form [ [key1, stuff1], [key2, stuff2],
For my German-language cycling podcasts overview I am about to scrape all feeds - of active and inactive podcasts. I stumble over a lot of feeds that are hidden behind walled gardens, especially Spotify is hiding all data and thus considere
#jsonparse across platforms
every network with a public tag surfaceFollow #jsonparse 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/jsonparse