#asciidoctorlitprog
Live, measured metrics for the hashtag #asciidoctorlitprog from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #asciidoctorlitprog
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 · mas.to (Mastodon public tags API) · fetched 2026-08-04 18:06 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-08-04 18:06 UTCNo related tags with measured usage found for #asciidoctorlitprog.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-08-04 18:06 UTCEverything below is measured over the latest 4 public posts (spanning ~61 hours).
Posting hours (UTC)
Languages: English (4)
Avg boosts / post: 0.5
Used together with
Top of the latest posts
I wanted to add to #AsciidoctorLitProg the possibility to produce a graph of the relative dependencies between code chunks, and while I can produce a #GraphViz file trivially, I can't seem to find a decent combination of layout options that
Probably the last stretch for today: v2.2 of #AsciidoctorLitProg, with a feature enhancement (runtime renaming of output files), and an important bugfix for when chunk names have <, & or > in them. https://github.com/Oblomov/asciidoctor-lit
(more >) As an example, the #AsciidoctorLitProg source itself now mixes #Ruby and #CSS (the CSS that we add to the woven outputs!) but comments in the CSS section must use the C-style format /* ... */, while in Ruby they use the hash sign #
#asciidoctorlitprog across platforms
every network with a public tag surfaceFollow #asciidoctorlitprog 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/asciidoctorlitprog