#jsonschema
Live, measured metrics for the hashtag #jsonschema from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #jsonschema
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 05:42 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 05:42 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 05:42 UTCEverything below is measured over the latest 40 public posts (spanning ~12169 hours).
Posting hours (UTC) — busiest: 08:00
Languages: English (29) · Russian (7) · Dutch (3)
Avg boosts / post: 0.7
Top of the latest posts
What is it with standards authors and their design approaches that they so often fall victim to monolithic specs, full of severe feature creep? Why are modern data/protocol standards still not more layered/modularized, with especially niche
@dvh laat zien dat hij all schema's uit de Open API Specs van de API's op apis.developer.overheid.nl heeft omgezet naar JSON Schema's. Dit levert een mooie inkijk in bestaande schema's vanuit verschillende organisaties. #oas #jsonschema
Lapidary-render 0.12.0 is now released. To the best of my knowledge it's the only #codeGenerator that properly handles #jsonSchema anyOf and allOf. Also has support for oneOf, but not per the specs. https://github.com/python-lapidary/lapida
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/jsonschema