#docsets
Live, measured metrics for the hashtag #docsets from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #docsets
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 11:13 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 11:13 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 11:13 UTCEverything below is measured over the latest 3 public posts (spanning ~2.8 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 0
Used together with
Top of the latest posts
Ok for anyone who's interested: https://github.com/drmorr0/zeal-docset-tools I have some ideas for other tools I'd like to add in the future, but the toc_fixer script makes the table-of-contents work for both Rust and Golang docsets. (YMMV
TLDR: The Rust docset _does_ include dashAnchors for ~everything, but the `path` value for a bunch of these fields in the docSet.dsidx sqlite3 search index looks like ``` <dash_entry_menuDescription=impl%3CT%3E%20Option%3CT%3E%20-%20std::op
Does anybody have experience with Rust docsets, tables of contents, and Zeal? I'm trying to figure out a weird issue. Update: I figured it out! #rust #zeal #dash #docsets
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/docsets