#yardoc
Live, measured metrics for the hashtag #yardoc from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #yardoc
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:16 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:16 UTCNo related tags with measured usage found for #yardoc.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 11:16 UTCEverything below is measured over the latest 10 public posts (spanning ~10935 hours).
Posting hours (UTC)
Languages: English (8) · German (2)
Avg boosts / post: 0.5
Top of the latest posts
@serge many of the projects we use in Python, like #Flask, are documented using #Sphinx, which can be configured to automatically generate API documentation from Python source code: https://www.sphinx-doc.org/en/master/tutorial/automatic-do
I think inline #documentation is an important tool to making software readable. It makes software maintainable, encourages future development and makes it easier to join the project as a developer. This is why I advocate for #mastodon to st
I'm thinking about asking on the #Mastodon issue tracker about introducing inline documentation using #yardoc or #rdoc to public functions on modules and classes. Was there any issue, discussion or call for this already? #MastodonDev
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/yardoc