#DSSSL
Live, measured metrics for the hashtag #DSSSL from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #dsssl
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:13 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:13 UTCNo related tags with measured usage found for #dsssl.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 09:13 UTCEverything below is measured over the latest 5 public posts (spanning ~17314 hours).
Posting hours (UTC)
Languages: English (5)
Avg boosts / post: 0
Top of the latest posts
@david_megginson @HugoHeagren Currently, I use https://github.com/docbook/xslTNG which depends on the open source home edition of saxon XSLT processor to convert DocBook XML to HTML/ePub, and use #CSS based publishing softwares like https:/
@callionica HTML before 4.0 was defined with SGML which gives it the flexibility of auto closing tags, but I doubt any #SGML / #DSSSL implementation is still useable today and if people would still be willing to learn it after the language
@juliobiason Actually, #CSS was not meant to fix #HTML. Independent stylesheets were planned from the beginning (as a parallel to #FOSI and #DSSSL for #SGML). (updated with the reference to FOSI, I knew that DSSL was just hacker-only non-co
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/dsssl