#circleci
Live, measured metrics for the hashtag #circleci from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #circleci
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 06:56 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 06:56 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 06:56 UTCEverything below is measured over the latest 40 public posts (spanning ~20192 hours).
Posting hours (UTC) — busiest: 21:00
Languages: English (33) · Japanese (3) · German (2) · Portuguese (1) · Polish (1)
Avg boosts / post: 0.7
Top of the latest posts
Almost forgot how to use #CircleCI's local job running tool. So handy. Also still a bit more usable than the thirdparty GHA equivalent (`act`).
How exactly do "blobless" clones work on #CircleCI? I've received their email about introducing a faster #git clone method and they're not kidding: for wxWidgets, using "blobless" brought clone time down from 82s to 14s in their environment
#CircleCI found a new (to me ?) path to #enshitification : start sending email notifications for *every* CI status (including "completed without error") instead of just failures (which was annoying already, mind you). Now in order to turn t
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/circleci