#regclient
Live, measured metrics for the hashtag #regclient from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #regclient
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 16:59 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 16:59 UTCNo related tags with measured usage found for #regclient.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 16:59 UTCEverything below is measured over the latest 3 public posts (spanning ~10578 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 0.7
Used together with
Top of the latest posts
To manage your own registry using the OCI APIs, there's a variety of client tooling. - I'm the author of #regclient (the regsync command is very useful for mirrors): https://regclient.org - #Crane is available from Google: https://github.co
It's release day for regclient. My favorite new feature is support for external referrers queries. This lets 3rd parties, like the security team, to maintain their own repositories for image metadata (think signatures, SBOMs, attestations).
I've been mostly heads down in the #OCI conformance test redesign. But I managed to ship a new #regclient release yesterday with a feature that will hopefully help the #zot registry. https://github.com/regclient/regclient/releases/tag/v0.11
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/regclient