#visecadatenleck
Live, measured metrics for the hashtag #visecadatenleck from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #visecadatenleck
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-08-04 03:06 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-08-04 03:06 UTCNo related tags with measured usage found for #visecadatenleck.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-08-04 03:06 UTCEverything below is measured over the latest 3 public posts (spanning ~243 hours).
Posting hours (UTC)
Languages: German (3)
Avg boosts / post: 1.7
Used together with
No co-used tags in the sample.
Top of the latest posts
Ursprüngliche Titel für den Artikel war: "Ich weiss, was Du letzten Sommer abgebucht hast." Aber das fanden meine Redigateure leider zu kryptisch. #VisecaDatenleck
What can possibly go wrong: die Schaffhauser Kantonalbank fand durch Nachfragen des Journalisten @SimonMuster (Schaffhauser AZ) heraus dass die Viseca falsche Angaben bezüglich der Sicherheitslücke machte. #VisecaDatenleck
Fiserv, der amerikanische Zulieferer bei Viseca und offenbar technisch verantwortlich für das Desaster, hat eine History in Sachen IT Security: https://cyberscoop.com/fiserv-bessemer-credit-union-lawsuit-cyber-consequences/ #VisecaDatenleck
#visecadatenleck across platforms
every network with a public tag surfaceFollow #visecadatenleck 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/visecadatenleck