#digitalservicescoordinator
Live, measured metrics for the hashtag #digitalservicescoordinator from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #digitalservicescoordinator
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-10-05 07:00 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-10-05 07:00 UTCNo related tags with measured usage found for #digitalservicescoordinator.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-10-05 07:00 UTCEverything below is measured over the latest 14 public posts (spanning ~22366 hours).
Posting hours (UTC) — busiest: 12:00
Languages: German (7) · English (6)
Avg boosts / post: 2.6
Top of the latest posts
Digital Services Act: Was hinter dem Veto des polnischen Präsidenten steckt https://netzpolitik.org/2026/digital-services-act-was-hinter-dem-veto-des-polnischen-praesidenten-steckt/ Polen tut sich schwer damit, den Digital Services Act voll
Morgen geht's im #Digitalausschuss übrigens um den Haushalt des Ministeriums im nächsten Jahr, und um den #DigitalServicesCoordinator #DSC ( =Umsetzung des #DSA, und alles, was auf Plattformen falsch läuft.) Leider alles ohne Öffentlichkeit
EDRi member @panoptykon Foundation fighting dubious lack of transparency in #Poland's selection of the #DigitalServicesCoordinator's leadership 💪 https://eupolicy.social/@panoptykon/115145932379104991 #DSC #UKE #DSA #DigitalServicesAct
#digitalservicescoordinator across platforms
every network with a public tag surfaceFollow #digitalservicescoordinator 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/digitalservicescoordinator