#dhconvalidator
Live, measured metrics for the hashtag #dhconvalidator from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #dhconvalidator
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-27 00:32 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-27 00:32 UTCNo related tags with measured usage found for #dhconvalidator.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 00:32 UTCEverything below is measured over the latest 10 public posts (spanning ~26410 hours).
Posting hours (UTC)
Languages: English (8) · German (2)
Avg boosts / post: 1
Top of the latest posts
Thanks for flagging this. Could you send the error details (and ideally your test ODT) to [email protected]? We'll take a look on our end and also raise the #DHConvalidator issue with @adho
@dh2026daejeon @adho I am down to running a test suite through the #DHConvalidator. Submitting ODT with multiple paragraphs of Lorem Ipsum in the “DH-Default” style results in a conversion error claiming that not a single of the required ch
The #DHConvalidator makes me want to kill myself. Again! The .odt templates generate endless errors and the .docx templates return only partial content on success! Any idea, @dh2026daejeon , @adho ? #DH2026 #DigitalHumanities #fail
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/dhconvalidator