- From: <bugzilla@jessica.w3.org>
- Date: Mon, 27 Oct 2014 09:46:09 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27055 --- Comment #15 from Sergey Konstantinov <twirl-team@yandex.ru> --- > It follows that the JavaScript program needs to obtain a new DRM-level > "license" at least hourly and also any time the user seeks the video > backwards (since the CDM isn't allowed by the DRM-level license to decode the > content twice). Why do you think it's useful to surface this implementation > detail to the user if the user-facing experience is that they get to use the > service for longer than an hour (until they cancel the subscription) and they > get to seek backwards? Because in such system user obviously cannot cache video to watch it offline or using poor internet connection. It breaks several important use cases like watching film in a tube or airplane. I as Web user *do* want to know about these *technical* restrictions. To summarize the discussion: EME brings in a Web inability to manage content; restrictions brought by EME (like you need to reinstate license each time you seek video backwards) are enigmatic even to experienced user leading to possible misunderstandings between consumers, content vendors, browser makers, and DRM system makers. Furthermore we could imagine fraud scenarios exploiting this inability. We understand that "product" licenses are quite different from "technical" ones, but we are talking about *technical* restrictions since *technical* restrictions are annoying people most. Though I'm proposing to standardize both. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 27 October 2014 09:46:11 UTC