#hedgedocleaks
Live, measured metrics for the hashtag #hedgedocleaks from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #hedgedocleaks
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-01 09:51 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-01 09:51 UTCNo related tags with measured usage found for #hedgedocleaks.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-08-01 09:51 UTCEverything below is measured over the latest 37 public posts (spanning ~26975 hours).
Posting hours (UTC) — busiest: 20:00
Languages: English (31) · German (6)
Avg boosts / post: 0.7
Top of the latest posts
HedgeDoc just did the fastest support in our history. Report to fix in ~25 min. And it was totally random that that worked out like this. :D #HedgeDoc #HedgeDocLeaks
Look at @innaytool developing HedgeDoc 2 on a totally normal setup. #HedgeDocLeaks
And it's time for a HedgeDoc 1 Release. How did this work again? #HedgeDocLeaks
#hedgedocleaks across platforms
every network with a public tag surfaceFollow #hedgedocleaks 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/hedgedocleaks