#cooperhate
Live, measured metrics for the hashtag #cooperhate from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #cooperhate
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-22 19:00 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-22 19:00 UTCNo related tags with measured usage found for #cooperhate.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-10-22 19:00 UTCEverything below is measured over the latest 2 public posts (spanning ~59 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0
Top of the latest posts
@antiware As always people can be right and wrong. It is just a personal presentation. A lot is very aposite. I enjoyed hearing what he had to say. There is in social media too much #cooperhate and schism and polarisation. We learnt from #c
@cazabon #Codeberg algorithm: If you type the same comment into the #pullrequest #PR descriptor field a few times you get rate limited: cannot do the PR. This was for preventing bot use. But I was using the same PR comment *manually* for id
#cooperhate across platforms
every network with a public tag surfaceFollow #cooperhate 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/cooperhate