#documentengineering
Live, measured metrics for the hashtag #documentengineering from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #documentengineering
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 09:07 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 09:07 UTCNo related tags with measured usage found for #documentengineering.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 09:07 UTCEverything below is measured over the latest 11 public posts (spanning ~21253 hours).
Posting hours (UTC)
Languages: English (10) · German (1)
Avg boosts / post: 1.5
Top of the latest posts
In my talk for the 2019 #XMLPrague paper “History and the Future of Markup” http://archive.xmlprague.cz/2019/files/xmlprague-2019-proceedings.pdf#page=335 I speculated about the use of #REXX as a language for #SGML tree manipulation. Last n
There’s still time to submit a long paper to ACM #DocEng25: share your document-related research and submit a paper by April 29! Short papers and demos are due June 17. (For all categories, abstracts are due a week before). #DocEng2025 #Doc
The irony is that they conclude that 200 dpi are enough, and 300 dpi give you a good safety margin. They stress that higher resolutions waste storage space, communication network bandwidth for file transmission, and processing power. But th
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/documentengineering