throwaway99797
|
3 years ago
|
on: Cloudflare Calls
WebRTC is end-to-end encrypted to the peer. So you're right, when you do actual peer to peer WebRTC between you and another user in a browser, you have end-to-end encrypted communication. When you go through a server, it's just another peer. So the word end maybe doesn't fit anymore, because it's a server that is the peer and they can decrypt the stream. Transcoding is pretty common at that stage because it's helpful for scaling.
throwaway99797
|
3 years ago
|
on: Cloudflare Calls
Cloudflare has to have access to the decrypted video just like Google Meet does, because browsers by default encrypt to the peer and they are the peer. After all these years there still isn't universal browser support for actual E2EE. What support does exist uses hacky APIs.
throwaway99797
|
3 years ago
|
on: Cloudflare Calls
Google missed their opportunity to do this: they've had Google Meet / Hangouts / ... for years. They have the same backend infrastructure that can scale to thousands and low latency to everywhere. Meet already does this with a custom Google protocol in the browser.
If Google had just opened their APIs, they could have provided this to everyone...
