Content protection (EME): Looking for early adopters

Hello! I'm looking for WebCodecs apps that are interested in content protection features (similar to EME, including copy protection, key management, HDCP, ...).

We have some interest expressed in #41, but that discussion quickly gets into weeds of various technical requirements. I'd like to take a step back. Developing these features is a significant undertaking. I'm looking to partner with a handful of early adopters to ensure we build it right and can maximize the impact for users ASAP.

Please note: this issue is about WebCodecs, not WebRTC. We are aware of interest in EME features for WebRTC. These are best handled by WebRTC APIs, so please file issues against those specs. WebCodecs strives to be coherent with other web APIs but is generally designed to be a low level API that is decoupled from WebRTC.

Lets not discuss technical details here!

Instead, please file a separate issue w/ a subject like "Content Protection: example.com" with details of your use case and requirements. Please reference this issue (#483) in your report to help us aggregate the requests.

From there I hope to identify overlapping features and areas where we can invest early to make the biggest difference. Thanks!

No files, tests, or entry points are named. This issue requests separate use-case reports from WebCodecs content-protection adopters, so a contributor would need to provide a report describing an application’s requirements rather than implement a defined change.