#throttlingharrassment
Live, measured metrics for the hashtag #throttlingharrassment from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #throttlingharrassment
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-08-03 08:25 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-08-03 08:25 UTCNo related tags with measured usage found for #throttlingharrassment.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-08-03 08:25 UTCEverything below is measured over the latest 3 public posts (spanning ~6.6 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 0.7
Used together with
Top of the latest posts
I'm heavily committed to using #QuoteBoosts / #QuoteTweets, for reasons I've already tooted. But I think my side of the argument has to step up and talk about #ThrottlingHarrassment if QB/QT's are implemented. Some suggestions: 1. Present a
@EeeeWooo We might also simultaneously implement features to allow targeted users to engage in #ThrottlingHarrassment. https://mastodon.online/@Carwil/109580295441460333
Okay, what have we learned? QT's have many uses. They can be a major tool in productive discussion and a major tool in a pile-on. In my view, disabling QT's is not the right solution to the dunking problem, given the many types of construct
#throttlingharrassment across platforms
every network with a public tag surfaceFollow #throttlingharrassment 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/throttlingharrassment