#intercal
Live, measured metrics for the hashtag #intercal from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #intercal
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-27 08:54 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-27 08:54 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 08:54 UTCEverything below is measured over the latest 20 public posts (spanning ~61714 hours).
Posting hours (UTC) — busiest: 02:00
Languages: English (19) · German (1)
Avg boosts / post: 1.4
Top of the latest posts
On April 1st 1999, CLC-INTERCAL 0.01 escaped into an unsuspecting world. Today, 25 years later, CLC-INTERCAL 1.00 escaped into the same unsuspecting world (we ARE really sorry!) What has changed? We've taken the escape number from 25 years
@leonerd This sounds like the conditional logic equivalent of #INTERCAL’s `COME FROM`: https://en.wikipedia.org/wiki/COMEFROM Of course, there’s an Acme #Perl module for it: https://metacpan.org/pod/Acme::ComeFrom
@Logical_Error Indeed, but there is a bit of a chicken and egg problem here: Unless it shows up prominently in a training data set, it won't matter, because the LLM won't know what to do with it. Vaguely related, has anybody tried to use Cl
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/intercal