#r4rs
Live, measured metrics for the hashtag #r4rs from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #r4rs
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-29 01:25 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-29 01:25 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 01:25 UTCEverything below is measured over the latest 2 public posts (spanning ~11836 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 3
Top of the latest posts
Many #FP languages compile down to C or LLVM IR and, from thence, down to binary. That is all well and good, but I think there is a simpler, better way: to target the classic #Scheme #R4RS as the IR, then use a modern optimising Scheme impl
Hot take: in terms of the language specified treated independently of the social process of standardization itself, everyone's beloved #r5rs is actually the worst post-#r4rs scheme, and #r6rs is easily the best and most revolutionary, hence
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/r4rs