#tdd
Live, measured metrics for the hashtag #tdd from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #tdd
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 · mas.to (Mastodon public tags API) · fetched 2026-10-14 01:07 UTC2 uses by 2 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-10-14 01:07 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-10-14 01:07 UTCEverything below is measured over the latest 40 public posts (spanning ~907 hours).
Posting hours (UTC) — busiest: 16:00
Languages: English (33) · Russian (3) · German (1)
Avg boosts / post: 1
Top of the latest posts
There's a demo on Steam and Itch if you want to try it. Getting the file explorer to behave like a game is pretty tricky, so please appreciate all the tests I had to write for it. #tdd
RE: https://mas.to/@voidbot/117348750063219291 #SoftwareDesign #DesignCodeTest #TDD
Watching a talk about frontend TDD and it's still annoying that vitest takes more than a second to run a simple React component test. From using node:test with native TypeScript support I am so used to super fast execution. However in front
#tdd across platforms
every network with a public tag surfaceFollow #tdd 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/tdd