#xmlsec
Live, measured metrics for the hashtag #xmlsec from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #xmlsec
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 10:03 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 10:03 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 10:03 UTCEverything below is measured over the latest 5 public posts (spanning ~13704 hours).
Posting hours (UTC)
Languages: English (5)
Avg boosts / post: 0.8
Top of the latest posts
On top of the #uppsala #XML library and #bergshamra #xmlsec library I have #gamlastan, the #SAML library https://crates.io/crates/gamlastan #identity Finally I can work on the applications I needed.
And if you need #XML #SECURITY then use https://pybergshamra.readthedocs.io/en/latest/ for all #xmlsec in pure #rust level in #python.
To the wider #XML and #XMLSEC folks can you please verify this example of #XSW attack and defense makes sense to you? https://github.com/kushaldas/secexample #security
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/xmlsec