#bbr
Live, measured metrics for the hashtag #bbr from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #bbr
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 18:10 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 18:10 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 18:10 UTCEverything below is measured over the latest 21 public posts (spanning ~37892 hours).
Posting hours (UTC) — busiest: 13:00
Languages: English (15) · Russian (3) · Swedish (1) · German (1)
Avg boosts / post: 0.3
Top of the latest posts
Weekend Reads * Recent Internet disruptions https://blog.cloudflare.com/a-recent-spate-of-internet-disruptions-july-2024 * IPv6 hypergiant infrastructure https://dl.acm.org/doi/10.1145/3656300 * OpenBSD and email server guide https://datasw
Ditch CUBIC's loss-based congestion. Enable TCP BBR on Linux 4.9+ for model-driven throughput without bufferbloat. Use fq qdisc for pacing and set tcp_congestion_control to bbr. Get the config snippet: #linux #tcp #bbr https://www.valtersit
Why a Direct, 500 Mbit Tailscale Link Only Gave Me 10 Mbit for One Stream Tailscale과 같은 Mesh VPN은 TCP 트래픽을 UDP로 캡슐화하는데, 무선 환경에서 발생하는 UDP 패킷 손실이 TCP의 기본 혼잡 제어 알고리즘인 CUBIC에 의해 과도한 속도 저하를 유발한다. 이 문제는 TCP 혼잡 제어를 BBR로 변경하면 해결되며, BBR은 손실을 혼잡으로 간주
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/bbr