#technicallytrue
Live, measured metrics for the hashtag #technicallytrue from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #technicallytrue
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-24 07:09 UTC0 uses by 0 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-24 07:09 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-10-24 07:09 UTCEverything below is measured over the latest 19 public posts (spanning ~31108 hours).
Posting hours (UTC) — busiest: 06:00
Languages: English (17) · Dutch (1) · Chinese (1)
Avg boosts / post: 1.1
Top of the latest posts
The UK army does not accept applicants aged six and under #technicallyTrue
World War 2 ended more than six years ago #technicallyTrue
Make a fire for a man and he will be warm for the night Light a man on fire and he will be warm for the rest of his life #technicallyTrue
#technicallytrue across platforms
every network with a public tag surfaceFollow #technicallytrue 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/technicallytrue