#acme
Live, measured metrics for the hashtag #acme from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #acme
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 05:21 UTC2 uses by 2 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 05:21 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 05:21 UTCEverything below is measured over the latest 40 public posts (spanning ~2233 hours).
Posting hours (UTC) — busiest: 15:00
Languages: English (28) · German (3) · Russian (3) · Spanish (2) · Italian (1) · Chinese (Taiwan) (1)
Avg boosts / post: 1.2
Top of the latest posts
Ten years of ACME certificates issuing and people have forgotten how unreliable and fucked it was before. *sigh* [If your ACME client is not able to handle a service outage correctly, get another client. srsly] #acme #letsencrypt
I use #plan9 #acme to write #oberon for #avr MCUs on macosx and #openBSD laptops with the occasional foray into doing #forth on #8051 mcus. This isn't normal, I know.
The 47-day certificate: faster treadmill, same broken foundation Managing TLS certificates has become pretty crazy: Over the years validity was cut down from several years to two years to one year to half a year now. In a few years it will
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/acme