#correspsearch
Live, measured metrics for the hashtag #correspsearch from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #correspsearch
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-09-30 13:37 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-09-30 13:37 UTCNo related tags with measured usage found for #correspsearch.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-09-30 13:37 UTCEverything below is measured over the latest 11 public posts (spanning ~20808 hours).
Posting hours (UTC)
Languages: German (6) · English (5)
Avg boosts / post: 1.9
Top of the latest posts
Wir waren fleißig Anfang des Jahres: Es gibt nun zwei Hilfeseiten, die Suchmöglichkeiten und Visualisierungsfunktionen von correspSearch ausführlich erläutern. Suche: https://correspsearch.net/de/hilfe-suchfunktionen.html Visualisierungen:
DH bubble Der Arbeitskreis Digitale Protokolleditionen (https://www.protokolleditionen.eu/) möchte eruieren, welche Anforderungen an ein Portal für Protokolle (in Anlehnung an #correspSearch https://correspsearch.net) gestellt werden. Hierz
@buber_korrespondenzen_digital @mungo_s_park @correspSearch this function library makes things easier (provided you use eXist-db)… The discussion on #correspSearch in the paper right before that yielded the question if CS would accept some
#correspsearch across platforms
every network with a public tag surfaceFollow #correspsearch 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/correspsearch