#rfc742

Live, measured metrics for the hashtag #rfc742 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 #rfc742

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.

$520.70/ year · 6-character #name
Claim #rfc742$520.70/yrBuy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
3
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 3
0
Avg reactions / post
Mastodon · last 3

Day-by-day usage

measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-29 13:50 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 13:50 UTC

No related tags with measured usage found for #rfc742.

Live pulse

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

Everything below is measured over the latest 3 public posts (spanning ~463 hours).

Top of the latest posts

  • @orangeacme #finger has an origin at least going back to 1971. #IETF #RFC742 was written to document the existing #fingerProtocol , as it was (implicitly) defined by software. I.e., finger had been around and was evolving AT LEAST 6 years b

    @reiver ⊼ (Charles) :batman:@[email protected]002022-12-09 22:43 UTCView post →
  • 2/ Two specifications were created for the #fingerProtocol: • #IETF #RFC742 (published in 1977) • #IETF #RFC1288 (published in 1991) Neither of them were about creating the finger-protocol. The finger-protocol existed and was evolving AT LE

    @reiver ⊼ (Charles) :batman:@[email protected]022022-11-28 08:01 UTCView post →
  • The #fingerProtocol — except without any 7-bit ASCII restrictions — that were (from a specification(s) point-of-view) added in #IETF #RFC1288 , but didn't exist in #IETF #RFC742 . ( #finger #fingerHole #fingerverse ) ( #unicode #utf8 )

    @reiver ⊼ (Charles) :batman:@[email protected]012022-11-20 15:46 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/rfc742