Here are thoughts on the latest developments in the WebRTC world.
Stop scrolling through thousands of getStats lines. Upload a webrtc-internals dump to rtcStats and AI tells you what went wrong on the call in under 30 seconds. Or query it from Claude Code and Cursor over MCP.
Compute Pressure is the browser's privacy-preserving CPU load signal. Here's what it means, how to use it, and how rtcstats-js already collects it side-by-side with your other WebRTC metrics.
Stop asking users to capture webrtc-internals manually. Use rtcstats-js with IndexedDB to store WebRTC stats locally and get dumps only when you need them.
