#softwarestandards
Live, measured metrics for the hashtag #softwarestandards from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #softwarestandards
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-10-02 05:33 UTCNo measured public usage for #softwarestandards in the last 7 days. That is a real result, and a good one to know: this hashtag is wide open right now. We show a dash before we ever show a made-up number. Browse the trending index for tags with live measurements.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-10-02 05:33 UTCNo related tags with measured usage found for #softwarestandards.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-10-02 05:33 UTCEverything below is measured over the latest 6 public posts (spanning ~12288 hours).
Posting hours (UTC)
Languages: English (5) · German (1)
Avg boosts / post: 3.3
Top of the latest posts
The JSONPath RFC 9535 has been published. https://www.rfc-editor.org/rfc/rfc9535.html That was 17 years since the original JSONPath blog post and a little over three years since a number of us started collaborating on an internet draft. Rea
The IETF have kindly cross-posted a minor variation of my post to their blog: https://www.ietf.org/blog/jsonpath-rfc/ #IETF #RFC9535 #JSONPath #SoftwareStandards
Non-deterministic behaviour in a specification can be a headache for testing. This updated post explores the non-determinism in the JSONPath RFC 9535, describes how the Compliance Test Suite is being upgraded to deal with non-determinism, a
#softwarestandards across platforms
every network with a public tag surfaceFollow #softwarestandards 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/softwarestandards