#qxmpp
Live, measured metrics for the hashtag #qxmpp from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #qxmpp
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-10-31 03: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 · mas.to (Mastodon public search API) · fetched 2026-10-31 03:39 UTCNo related tags with measured usage found for #qxmpp.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-10-31 03:39 UTCEverything below is measured over the latest 2 public posts (spanning ~2658 hours).
Posting hours (UTC)
Languages: English (1)
Avg boosts / post: 0
Used together with
Top of the latest posts
@brie @nextcloud @lazarus There have been attempt to create other clients, first shmoose that managed to support OMEMO but the author went to other projects, then an attempt to first bring it to #qxmpp then port #kaidan (also dropped). #con
I kept it quiet yesterday, but it was a big day for me. For the first time ever I was able to send and receive an #omemo encrypted message with my messenger #squawk. It's not really a big deal in general but it's a huge event for me. Now to
#qxmpp across platforms
every network with a public tag surfaceFollow #qxmpp 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/qxmpp