#blocksTor
Live, measured metrics for the hashtag #blocksTor from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #blockstor
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-07-30 21:20 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-07-30 21:20 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-30 21:20 UTCEverything below is measured over the latest 3 public posts (spanning ~11405 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 0.7
Top of the latest posts
@atomicpoet Its not just the domain name of the instance itself that we need to be mindful of but also the #CDN that the server is using for images. Many instances use a seperate CDN. The instance we are on uses what we understand to be a p
So apparently #Rumble is blocked in #France. …if only it worked over #Tor, right? (Hint: It doesn't— at least not last time we tested it.) #surveillance #massSurveillance #blocksTor
@sexybiggetje We also list things like whether a site is insecure which results in a CAUTION mark rather than a full BLOCKMARK. We also have a #blocksTor marker, which gives it a BLOCKMARK.
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/blockstor