#xmlresolver
Live, measured metrics for the hashtag #xmlresolver from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #xmlresolver
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 · mastodon.online (Mastodon public tags API) · fetched 2026-10-22 15:39 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-10-22 15:39 UTCNo related tags with measured usage found for #xmlresolver.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-10-22 15:39 UTCEverything below is measured over the latest 18 public posts (spanning ~31343 hours).
Posting hours (UTC) — busiest: 15:00
Languages: English (18)
Avg boosts / post: 1.3
Used together with
Top of the latest posts
XML Resolver version 6.1.0. Yes, it’s ready. #XML #XMLResolver #Java #CSharp #MarkupMonday https://so.nwalsh.com/2026/08/31-xmlresolver
At the intersection of pain and suffering. There are Unix filesystems and Windows filesystems. There are Java URI objects and C# URI objects. There are file: URIs. And they all intersect in the XML Resolver. #XMLResolver #MarkupMonday https
XML Resolver version 6.0.23. Closing in on 6.1, this release exercises the new build infrastructure, mitigates a couple of Microsoft CVEs in the C# resolver, and adds support for “new” HTTP status codes in the Java resolver. #XML #XMLResolv
#xmlresolver across platforms
every network with a public tag surfaceFollow #xmlresolver 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/xmlresolver