#htcpcp
Live, measured metrics for the hashtag #htcpcp from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #htcpcp
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 · mastodon.online (Mastodon public tags API) · fetched 2026-09-25 17:57 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-09-25 17:57 UTCNo related tags with measured usage found for #htcpcp.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-09-25 17:57 UTCEverything below is measured over the latest 7 public posts (spanning ~24126 hours).
Posting hours (UTC)
Languages: English (3) · German (2) · Chinese (2)
Avg boosts / post: 0.4
Top of the latest posts
@dyfustic Activate Hyper Text Coffee Pot Control Protocol ! #HTCPCP
Today I (re-)learned about the “418 I’m a Teapot” [1] error code, which was first codified in the April’s fools issue of Internet request for comments for 1998. RFC2324 [2] describes the Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0),
I continue to be disappointed that the 418 bus route does not have, nor has ever had, teapots on board. #HTCPCP
What “htcpcp” means
WikipediaThe Hyper Text Coffee Pot Control Protocol (HTCPCP) is a facetious communication protocol for controlling, monitoring, and diagnosing coffee pots. As part of Internet Engineering Task Force's Request for Comments, RFC 2324 is published on 1 April 1998 as an April Fools' Day RFC, as part of an April Fools prank. An extension, HTCPCP-TEA, was published as RFC 7168 on 1 April 2014 to support brewing teas, also as an April Fools' Day RFC in error 418.
“Hyper Text Coffee Pot Control Protocol” on Wikipedia (CC BY-SA) →#htcpcp across platforms
every network with a public tag surfaceFollow #htcpcp straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/htcpcp