Three numbers per row now: RTT, loss%, jitter, plus path tag. Loss is computed as a delta vs the prior poll (not lifetime cumulative) so a spike during chops shows immediately instead of being averaged into a session-long denominator. Row colour bumps to the worst of the three: green RTT with 5% loss reads red. Reading guide: - RTT < 50 / loss < 0.5% / jitter < 20ms → green (clean) - RTT < 150 / loss < 2% / jitter < 50ms → yellow - otherwise → red What pattern correlates with your chops: - loss spikes + green RTT → network: TURN or upstream queue - jitter spikes + clean loss → buffering / Wi-Fi micro-bursts - all clean but chops continue → source-side (PulseAudio loopback, encoder starvation) |
||
|---|---|---|
| .. | ||
| blog | ||
| fonts | ||
| chat.html | ||
| host-your-own.html | ||
| how-it-works.html | ||
| index.html | ||
| kernel.html | ||
| stamp.js | ||
| zebra-audio.html | ||
| zebra-spaces.html | ||