#rfc8259
Live, measured metrics for the hashtag #rfc8259 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #rfc8259
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-28 20:34 UTC1 uses by 1 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-28 20:34 UTCNo related tags with measured usage found for #rfc8259.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 20:34 UTCEverything below is measured over the latest 6 public posts (spanning ~10282 hours).
Posting hours (UTC)
Languages: English (6)
Avg boosts / post: 1.3
Top of the latest posts
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
There is a larger discussion about fixed-point numbers versus floating-point numbers. And that, ALL programming-languages should have fixed-point numbers built into them. And that, programmers should be warned against using floating-point n
fennel-json is my #JSON parser written completely in #Fennel #lisp. It strictly complies with #RFC8259, the spec for JSON. I'm licensing it MIT, same as the Fennel language https://codeberg.org/ryanprior/fennel-json
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/rfc8259