#Datenpflege
Live, measured metrics for the hashtag #Datenpflege from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #datenpflege
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.online (Mastodon public tags API) · fetched 2026-10-04 00:47 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-10-04 00:47 UTCNo related tags with measured usage found for #datenpflege.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-10-04 00:47 UTCEverything below is measured over the latest 24 public posts (spanning ~32251 hours).
Posting hours (UTC) — busiest: 10:00
Languages: German (24)
Avg boosts / post: 0.6
Top of the latest posts
ok... die letzten Daten vom Googleaccount gezogen (da waren noch Bilder drauf 🫣), die aussortiert und in die vorhandene Bilderbibliothek eingepflegt (teilweise... 😅). Und dann ist mir aufgefallen das auch noch Browserlesezeichen auf dem G
Sachbearbeiter*in (m/w/d) Servicebereich Medienbearbeitung, Team Ausgabenmonitoring und Open Access, EG 10 TV-L, unbefristet, Vollzeit | https://jobs.uni-bielefeld.de/job/view/5160/sachbearbeiter-in-m-w-d-servicebereich-medienbearbeitung-te
Bibliotheksangestellte*r, Voll- oder Teilzeit; unbefristet; TV-L 8, Kennziffer TUV2604-01 | https://www.stellenwerk.de/koeln/bibliotheksangestellter-260507-268531 | https://bibliojobs.eu/stellenangebote/124465/ #bibliojobs #Bestandsorganisa
#datenpflege across platforms
every network with a public tag surfaceFollow #datenpflege 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/datenpflege