#historikerstreit2
Live, measured metrics for the hashtag #historikerstreit2 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #historikerstreit2
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 · mastodon.social (Mastodon public tags API) · fetched 2026-08-03 00:14 UTCNo measured public usage for #historikerstreit2 in the last 7 days. That is a real result, and a good one to know: this hashtag is wide open right now. We show a dash before we ever show a made-up number. Browse the trending index for tags with live measurements.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-08-03 00:14 UTCNo related tags with measured usage found for #historikerstreit2.
Live pulse
measured · Mastodon tag timeline · fetched 2026-08-03 00:14 UTCNo recent public posts found for #historikerstreit2 on Mastodon. Nothing measured, so nothing shown.
What “historikerstreit2” means
WikipediaThe Historikerstreit was a dispute in the late 1980s in West Germany between conservative and left-of-center academics and other intellectuals about how to incorporate Nazi Germany and the Holocaust into German historiography, and more generally into the German people's view of themselves. The dispute was initiated with the Bitburg controversy, which related to a commemorative service at a German military cemetery where members of the Waffen-SS were buried. The service was attended by Preside
“Historikerstreit” on Wikipedia (CC BY-SA) →#historikerstreit2 across platforms
every network with a public tag surfaceFollow #historikerstreit2 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/historikerstreit2