#rfc7159

Live, measured metrics for the hashtag #rfc7159 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.

hashtag.org network · sponsored

Own #rfc7159

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.

$240.06/ year · 7-character #name
Claim #rfc7159 — $240.06/yr→Buy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
5
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 5
1.6
Avg reactions / post
Mastodon · last 5

Day-by-day usage

measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-29 01:49 UTC
0
07-23
0
07-24
0
07-25
0
07-26
0
07-27
0
07-28
0
07-29

0 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-29 01:49 UTC

No related tags with measured usage found for #rfc7159.

Live pulse

measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 01:49 UTC

Everything below is measured over the latest 5 public posts (spanning ~27479 hours).

Posting hours (UTC)

00:0012:0023:00

Languages: English (5)

Avg boosts / post: 1.6

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

    @reiver ⊼ (Charles) :batman:@[email protected]♥ 4↻ 62026-02-22 18:00 UTCView post →

  • 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

    @reiver ⊼ (Charles) :batman:@[email protected]♥ 2↻ 02026-02-22 18:11 UTCView post →

  • This is likely (directly or indirectly) the fault of a single paragraph in IETF RFC-7159 / RFC-8259 (shown in the attached screen-shot). (And note that, there is a difference between JSON and IETF JSON. JSON did not have this. IETF JSON doe

    @reiver ⊼ (Charles) :batman:@[email protected]♥ 1↻ 02026-02-22 18:05 UTCView post →

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/rfc7159