- How Zoom’s web client avoids using WebRTC (DataChannel Update)
- How to add virtual background transparency in WebRTC
- Am I behind a Symmetric NAT?
- Computer Vision on the Web with WebRTC and TensorFlow
- Open Source Cloud Gaming with WebRTC
- How is WebRTC doing and who is driving usage? (Hint: Google Meet)
- True End-to-End Encryption with WebRTC Insertable Streams
Popular this Month
I have been looking at these Chrome usage statistics available on chromestatus.com for a while together with Tsahi Levent-Levi for WebRTC Insights but they are too fascinating to keep them behind our paywall. Let’s do some coffee ground reading on the usage of a number of important APIs and what it tells us about what drives WebRTC in Chrome:
Google Meet.
Meet (or back in the day Hangouts) is a major driver for WebRTC to Chrome. It is no secret Google invests heavily in this area – surprisingly the only major party doing so. The data shows why. ...
webrtcH4cKS: ~ How to add virtual background transparency in WebRTC
There is a cool new feature everyone has been trying to implement – background transparency. Virtual backgrounds have been around for a while. Rather than inserting a new background behind user(s), transparency removes the background altogether, allowing the app to place users over a screen share or together in a shared environment. There doesn’t seem to be a universal name for this feature. Zoom calls it Immersive View. Microsoft calls it Together Mode. RingCentral calls them overlays. Virtual green screens or newscaster mode are other names. ...
One of WebRTC’s great features is its mandated strong encryption. Encryption mechanisms are built-in, meaning developers don’t (often) need to deal with the details. However, these easy, built-in encryption mechanisms assume you have: 1) media is communicated peer-to-peer and 2) a secure signaling channel setup. Most group-calling services make use of a media server device, like a Selective Forwarding Unit (SFU) that terminate and re-encrypt, preventing the end-to-end encryption (e2ee). As we have covered here before, WebRTC e2ee is still possible with new APIs like Insertable Streams. That addresses the first assumption, but what about the second? How does one set up secure signaling for e2ee? ...
webrtcH4cKS: ~ Apple’s not so private relay fails with WebRTC
webrtcH4cKS: ~ Identifying Shared Tabs using Capture Handle (Elad Alon)
Introduction to capture handle - a new Chrome Origin Trial that lets a WebRTC screen sharing application communicate with the tab it is capturing. Examples use case discussed include detecting self-capture, improving the use of collaboration apps that are screen shared, and optimizing stream parameters of the captured content.
