#JSDocs
Live, measured metrics for the hashtag #JSDocs from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #jsdocs
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-28 11:37 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-28 11:37 UTCNo related tags with measured usage found for #jsdocs.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 11:37 UTCEverything below is measured over the latest 6 public posts (spanning ~13007 hours).
Posting hours (UTC)
Languages: English (6)
Avg boosts / post: 0.5
Top of the latest posts
If using Typescript means you want to write less Unit Tests then, actually, I'm all for it. Type away, with JSDoc comments. But I'm still making you write end-to-end functional browser tests. #typescript #unitTests #javaScript #types #typin
If you think #ai is good at writing #documentation (comments, #JSDocs, commit messages etc.), you misunderstood the whole concept of documentation.
@thilo I've not used external definitions much personally, except when I need to import a type from a library. @enhance_dev does a great job of using #JSDoc for types in their docs. @see: https://enhance.dev/docs/learn/practices/types #jsdo
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/jsdocs