#xsltproc
Live, measured metrics for the hashtag #xsltproc from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #xsltproc
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 16:53 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 16:53 UTCNo related tags with measured usage found for #xsltproc.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 16:53 UTCEverything below is measured over the latest 2 public posts (spanning ~173 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0
Top of the latest posts
TIL that #xsltproc (on my system) only supports #XSLT version 1.1. I learned this because the `replace( … )` function apparently requires XSLT version 2.0. I want the `replace( … )` function because #IANA put two comma separated addresses i
RE: https://genart.social/@davidcarew/116178444886600923 I absolutely agree with @davidcarew about usefulness of #sed and #awk. I am starting to dabble with #xsltproc for some #XML aware bulk modification. I used #XSLT to convert an XML fil
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/xsltproc