#l4s
Live, measured metrics for the hashtag #l4s from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #l4s
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.social (Mastodon public tags API) · fetched 2026-07-27 07:20 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.social (Mastodon public search API) · fetched 2026-07-27 07:20 UTCLive pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-07-27 07:20 UTCEverything below is measured over the latest 24 public posts (spanning ~26731 hours).
Posting hours (UTC) — busiest: 19:00
Languages: English (21) · Chinese (2) · German (1)
Avg boosts / post: 0.6
Top of the latest posts
To learn how the sausage is made, see RFC9330 "Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: Architecture" https://datatracker.ietf.org/doc/rfc9330/ #networking #NetworkingProtocols #RFC #IETF #L4S
Based on this data, adoption of classic ECN (ECT0) is low. That said, I am excited for #L4S (ECT1) adoption in the future. #firefox 's #quic stack reflects all of the ECN marks, including ECT1. Thus Firefox is ready for L4S on the receive p
Here are the kick-off slides from the "#QoE / #QoS: #BandwidthIsALIE panel discussion at #WISPAPALOOZA 2025 by @wispanews with a lot of good reading about #bufferbloat, #latency, #jitter, #bandwidht and more: https://docs.google.com/present
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/l4s