#DocEng
Live, measured metrics for the hashtag #DocEng from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #doceng
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-11-06 04:27 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-11-06 04:27 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-11-06 04:27 UTCEverything below is measured over the latest 13 public posts (spanning ~30962 hours).
Posting hours (UTC) — busiest: 07:00
Languages: English (11) · German (2)
Avg boosts / post: 1.9
Top of the latest posts
@faassen Interesting observation, I consider the #XMLPrague community rather young. The average is probably 20 years less than the audience average age at #DocEng. There are people out there doing in fact document engineering, but they’re e
BTW, the proceedings of #DocEng2026 are open access and available in the ACM Digital Library. https://doi.org/10.1145/3820755 #DocEng
Opening of #DocEng2026 at the University of Fribourg. https://doceng.org/doceng2026 #DocEng
#doceng across platforms
every network with a public tag surfaceFollow #doceng 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/doceng