WebRTC

Mozilla has released Firefox 157, its latest stable browser version, headlined by a visual refresh of the interface and support for hardware-accelerated AV1 decoding in WebRTC video calls. The update should reduce CPU load and improve battery life during video conferencing on machines with capable hardware. Coverage so far comes from tech outlets such as Phoronix, with early reader discussion focused on the redesigned UI.

Google has patched a use-after-free vulnerability in WebRTC in Google Chrome, tracked as EUVD-2026-93843 with a CVSS score of 8.8. The flaw, fixed in Chrome 155.0.8059.39, could have let a remote attacker execute arbitrary code inside the browser's sandbox via a specially crafted HTML page. Security trackers updated the entry on 6 October 2026.

A technical breakdown explains how three video ingest protocols — RTMP, SRT and WHIP — actually work, highlighting their latency differences and the situations each is best suited for. RTMP remains common for standard streaming uploads, SRT offers reliable low-latency transport over poor networks, and WHIP brings WebRTC-based ingest for near-real-time use cases. The guide is aimed at developers and engineers choosing transport for live video.

A technical overview of PPCDN is circulating among developers, detailing how its three-tier design combines origin servers, edge nodes and the ppcenter control layer to handle publishing, content delivery and scheduling. The write-up argues that self-hosting this open-source setup can be more cost-effective than relying on large commercial cloud CDN services.

A new technical explainer details how simulcast encoding lets a single published video stream carry multiple quality layers, allowing servers to deliver the appropriate resolution to each viewer on demand. The approach avoids repeated transcoding, cutting bandwidth costs and processing overhead for live video platforms. The walkthrough is part of an ongoing series aimed at developers working with WebRTC and video delivery systems.