#http3
Live, measured metrics for the hashtag #http3 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #http3
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 20:34 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 20:34 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 20:34 UTCEverything below is measured over the latest 40 public posts (spanning ~4679 hours).
Posting hours (UTC) — busiest: 10:00
Languages: English (31) · Russian (6) · French (1) · Indonesian (1) · German (1)
Avg boosts / post: 1
Top of the latest posts
Spent way too long getting HTTP/3 working on FreeBSD with nginx, so I wrote it all up. The highlights: stock OpenSSL silently breaks QUIC at the HTTP/3 framing layer (the TLS handshake succeeds, so openssl s_client lies to you). eBPF worker
Our Mastodon instance burningboard.net now supports HTTP/3 (QUIC). HTTP/3 replaces TCP with UDP as its transport protocol, offering lower latency and better performance, especially on lossy or low-bandwidth networks. https://http3check.net/
Oops, I’m accidentally writing a new book on modern networking (QUIC, HTTP3, Sans-IO, etc.) There was a gap in the literature. Networking content is either a decade plus old or RFCs which aren’t always easy reads. A fundamental thread is th
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/http3