#princexml
Live, measured metrics for the hashtag #princexml from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #princexml
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 22:08 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 22:08 UTCNo related tags with measured usage found for #princexml.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 22:08 UTCEverything below is measured over the latest 4 public posts (spanning ~25130 hours).
Posting hours (UTC)
Languages: English (2) · French (2)
Avg boosts / post: 1.5
Top of the latest posts
At the moment, your best option for doing prosumer or lower DTP … is a time machine. Microsoft Publisher — which was pretty bad — is going end of life. Affinity’s products, including Designer, cannot currently be purchased and it’s unclear
Pour créer les #PDF sur Paheko.cloud, nous utilisons le logiciel #PrinceXML, édité par le créateur de #CSS. C'est un outil très efficace et agréable à utiliser, mais non libre. En conséquence, pour améliorer les outils libres de création de
@julientaq @spaceninja Do you happen to know how well those might support PDF/UA or WCAG 2 standards for accessible PDFs? Anything that doesn't is a non-starter for me. iText and PrinceXML both claim to support PDF/UA. On the WeasyPrint sit
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/princexml