Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This diagram and most of non-normative parts of the spec are a deliberate red herring. The purpose of these is to derail discussion about DRM restrictions by saying that any restrictions are optional.

However, during discussions at W3C Netflix representatives confirmed that their implementation doesn't work like this. They are only interested in "strong" DRM model in which the player is not trusted and has no ability to see decrypted data, so it can't even use its regular HTML5 codec to decode it.



On Android they feed it directly to the OS codecs except for 4K video so they can't really care that much.


Thanks for the clarification! Can I upvote you twice?




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: