#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-10-30 12:44 UTC13 uses by 11 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-30 12:44 UTCNo related tags with measured usage found for #technicalwriting.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-10-30 12:44 UTCEverything below is measured over the latest 40 public posts (spanning ~1702 hours).
Posting hours (UTC) — busiest: 11:00
Languages: English (38) · German (1) · Spanish (1)
Avg boosts / post: 1.4
Top of the latest posts
More people should know about the idea of intralingual translation and intersemiotic translation: https://en.wikipedia.org/wiki/On_Linguistic_Aspects_of_Translation It's very useful to know about even if you're completely outside the field.
More than words While I’ve done a lot of reference documentation writing, my favourite type of work is writing tutorials and “how to” content. I enjoy the challenge of understanding a technology and an audience, then explaining the technolo
Just finished a huge post on how I've narrowed down my #emacs / #orgmode use for teaching based on #technicalwriting principles over the past several years. There's a ton in there and I hope somebody finds it helpful. Please feel free to le
#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