#criticaltechnicalpractice
Live, measured metrics for the hashtag #criticaltechnicalpractice from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #criticaltechnicalpractice
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-11-09 07:27 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-11-09 07:27 UTCNo related tags with measured usage found for #criticaltechnicalpractice.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-11-09 07:27 UTCEverything below is measured over the latest 10 public posts (spanning ~9816 hours).
Posting hours (UTC)
Languages: English (10)
Avg boosts / post: 6.2
Top of the latest posts
We're the Department of Digital Humanities at King's College London. By way of #introduction here are some tags for our research, teaching and collaborations 🏷 #ai #algorithmstudies #archives #artificialintelligence #commodon #computationa
an #introduction ... 📝 my work explores the role of digital data, methods and infrastructures in the composition of collective life. i'm currently focusing on... - 📘 a book on public data practices - 🌳 arts-based digital methods for expl
GaTech Digital Media #PhD apps are due Dec 15! I'm looking for a student interested in studying how to create environments & infrastructures to help people to do the work of #TechEthics, using qualitative & design methods. I usually approac
#criticaltechnicalpractice across platforms
every network with a public tag surfaceFollow #criticaltechnicalpractice 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/criticaltechnicalpractice