#Ortsdaten
Live, measured metrics for the hashtag #Ortsdaten from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #ortsdaten
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-07-28 23:58 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-07-28 23:58 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 23:58 UTCEverything below is measured over the latest 11 public posts (spanning ~22843 hours).
Posting hours (UTC)
Languages: German (8) · English (3)
Avg boosts / post: 4.2
Top of the latest posts
Aufzeichnung zum Zoom-Meeting im Oktober: Historische Ortsdaten Die Entwicklung eines Minimaldatensatzes für Historische Ortsdaten haben Sophie Döring, Felix Köther und Anne Purschwitz im Oktober-Zoom-Meeting des Vereins für Computergenealo
Vor 11 Jahren (als ich noch im Vorstand von #CompGen war) veröffentlichten Jesper Zedlitz und ich den Beitrag "Das Genealogische Ortsverzeichnis (GOV). Eine Einführung" (Archivar, 2014, Heft 3, S. 282–289). Damals ohne nennenswerte Resonanz
📍 Clustertreffen CC Data Capture and Creation 🗓 10.03.2026 | 14:30–16:00 | online Mit Sophie Döring (Uni Göttingen) Thema: Historische Ortsdaten & #Minimaldatensatz Wie schaffen wir nachhaltige, interoperable #Standards für #Ortsdaten? 💬
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/ortsdaten