#clockss
Live, measured metrics for the hashtag #clockss from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #clockss
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.social (Mastodon public tags API) · fetched 2026-07-29 13:25 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.social (Mastodon public search API) · fetched 2026-07-29 13:25 UTCLive pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-07-29 13:25 UTCEverything below is measured over the latest 24 public posts (spanning ~23421 hours).
Posting hours (UTC) — busiest: 11:00
Languages: English (21) · Dutch (3)
Avg boosts / post: 3.2
Top of the latest posts
Time to update the CLOCKSS? Why hasn't Heterocycles been released yet? https://rossmounce.co.uk/2024/06/11/time-to-update-the-clockss/ cc @chartgerink @Luke_Drury #Heterocycles #CLOCKSS #Governance #Community #ScienceAsAPublicGood
I emailed the executive director of CLOCKSS late last Friday to ask some basic questions about #Heterocycles No reply yet, but I'm hopeful.. #CLOCKSS
It's easier than ever for #OpenAccess journals to ensure their long-term #preservation. https://blog.doaj.org/2023/02/09/project-jasper-a-progress-report/ Thanks to the latest upgrade of #Project_Jasper from the #DOAJ, #CLOCKSS, @internetar
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/clockss