#qpack
Live, measured metrics for the hashtag #qpack from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #qpack
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-27 06:10 UTC4 uses by 4 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-27 06:10 UTCNo related tags with measured usage found for #qpack.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-10-27 06:10 UTCEverything below is measured over the latest 8 public posts (spanning ~31191 hours).
Posting hours (UTC)
Languages: English (7) · Russian (1)
Avg boosts / post: 0.4
Top of the latest posts
A small HTTP/3 HEADERS frame can become a large in-memory request. FoxIO found affected QPACK stacks checking compressed input, enforcing limits too late, or missing cumulative accounting. The engineering rule is broader than this bug: budg
Security researchers at FoxIO have disclosed a vulnerability affecting HTTP/3 QPACK implementations across multiple libraries, where unconstrained or late-enforced decompression limits allow a single crafted connection to trigger massive me
HTTP/3 Servers Vulnerable to Crashing via QPACK Flaws A single malicious connection can crash many HTTP/3 servers due to flaws in QPACK header compression, which allows attackers to send a small batch of compressed headers that expand into
#qpack across platforms
every network with a public tag surfaceFollow #qpack 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/qpack