#technicalwriting
Live, measured metrics for the hashtag #technicalwriting from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #technicalwriting
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 · mastodon.online (Mastodon public tags API) · fetched 2026-09-14 19:57 UTC6 uses by 5 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-09-14 19:57 UTCNo related tags with measured usage found for #technicalwriting.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-09-14 19:57 UTCEverything below is measured over the latest 40 public posts (spanning ~2209 hours).
Posting hours (UTC) — busiest: 11:00
Languages: English (38) · German (1) · Spanish (1)
Avg boosts / post: 1.5
Top of the latest posts
Where’s the holistic AI productivity data? For most of my career I ran a very small company. When you run a tiny company your resources (both time and money) are limited, and you want to use them on the things that will have the most impact
Here’s why contextual and use case-based documentation matters a lot when it comes to APIs: “The problem is that documentation is often organized entirely around individual endpoints with very little cross-endpoint guidance, implicit prereq
510 daily posts on The Main Thread taught me two things: consistency works, and agents only help when verification keeps up. I am changing the cadence now. Still Quarkus, Java, standards, and agentic engineering. More room for tests, exampl
#technicalwriting across platforms
every network with a public tag surfaceFollow #technicalwriting 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/technicalwriting