Open MarkusZoppelt opened 4 years ago
chromium has insertable streams implemented, but under an "origin" lock (meaning it is enabled on a per-site basis). we've done that for the nightly branch and of our internal site, are testing, have found a few issues, and investigating... hopefully we will have something to report, but i don't have an ETA as to when... sorry!
Consider adding support for WebRTC Insertable Streams
This is currently an experimental web feature of the Chrome Beta. It is needed for easy end-to-end encrypted (e2ee) webstreams, e.g., for Jitsi or other solutions.
=== This API enables the insertion of user-defined processing steps in the encoding and decoding of a WebRTC MediaStreamTrack.
Allow applications to insert custom data processing. A specific use case we want to support is end-to-end encryption of the encoded data transferred between RTCPeerConnections via an intermediate server.
Documentation https://github.com/alvestrand/webrtc-media-streams
Specification Public discussion