#openrepos2025
Live, measured metrics for the hashtag #openrepos2025 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #openrepos2025
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-31 21:08 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-31 21:08 UTCNo related tags with measured usage found for #openrepos2025.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-31 21:08 UTCEverything below is measured over the latest 23 public posts (spanning ~9237 hours).
Posting hours (UTC) — busiest: 14:00
Languages: English (15) · German (5) · Finnish (1) · Chinese (Taiwan) (1) · French (1)
Avg boosts / post: 2.3
Top of the latest posts
This is a really excellent talk at #openrepos2025 by Ben Zhao about the limits of and misconceptions about LLMs, that is tailored for the #libraries #archives and #digitalpreservation crowd. He focuses in on how they work, and don't work --
We sadly missed this year's Open Repositories conference, which was organised in Chicago a couple of weeks ago. But you can get some idea of the topics that were being discussed by browsing the presentation slides, which are now available i
本月中旬在芝加哥大學舉行的第二十屆開放儲存庫國際會議 (20th International Conference on Open Repositories, #openrepos2025) 中，中央研究院的研究資料寄存所 (depositar) 團隊由王禮芳同學報告 "Automated Data Analytics: A Statistical Dashboard Built with GitLab CI/CD for a Data Repository Based on
#openrepos2025 across platforms
every network with a public tag surfaceFollow #openrepos2025 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/openrepos2025