#jsonresume
Live, measured metrics for the hashtag #jsonresume from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #jsonresume
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 04:31 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 04:31 UTCNo related tags with measured usage found for #jsonresume.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 04:31 UTCEverything below is measured over the latest 12 public posts (spanning ~28615 hours).
Posting hours (UTC) — busiest: 14:00
Languages: English (11) · French (1)
Avg boosts / post: 1.3
Top of the latest posts
Not me forking JsonResume to add a `pronouns` field they don't wanna add :blobfox3c: https://github.com/AverageHelper/resume-schema #resume #JsonSchema #JsonResume #git #fork #foss
Does it also drive you crazy that your #resume and your job applications are not connected by an open data format? Do you feel antsy combining formatting and content in the same artifacts just so you can apply for jobs? Does building a cont
My website is now entirely built with #Zola using #Nix including my resume which is created from a #Dhall configuration extending the #JSONResume schema ! Feel free to review my Nix files 🥰 https://github.com/gaelreyrol/dhall-resume/blob/m
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/jsonresume