#otpor
Live, measured metrics for the hashtag #otpor from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #otpor
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-13 20:44 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-13 20:44 UTCNo related tags with measured usage found for #otpor.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-10-13 20:44 UTCEverything below is measured over the latest 16 public posts (spanning ~16545 hours).
Posting hours (UTC) — busiest: 12:00
Languages: English (1)
Avg boosts / post: 0.6
Top of the latest posts
In the case of Serbia in the late 1990s, it was not hard for Otpor and other resistance groups to get a majority of the population to agree that Milosevic should go. A huge portion of the public already detested the regime. With the economy
As it built up to an electoral push that would be backed by mass noncompliance, Otpor avoided centralizing around mass marches in Belgrade; instead, participants kept their actions varied and unexpected. —Mark Engler and Paul Engler, This I
The replication of a core DNA is something that happens naturally in mass movements. As protests spread, participants pick up common beliefs, slogans, and practices. But absent conscious deliberation about what the norms of a movement shoul
What “otpor” means
WikipediaOtpor was a political organization in Serbia from 1998 until 2004.
“Otpor” on Wikipedia (CC BY-SA) →#otpor across platforms
every network with a public tag surfaceFollow #otpor 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/otpor