- From: <bugzilla@jessica.w3.org>
- Date: Fri, 17 Oct 2014 17:50:15 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27055 --- Comment #5 from Mark Watson <watsonm@netflix.com> --- (In reply to Domenic Denicola from comment #4) > I think discussing this as "fraud" is taking the wrong approach. We're > mostly interested in the user getting this extra transparency into what > permissions they are granted. > > You may be right that this is not useful to the majority of users---in the > same way the majority of users do not actually click the lock icon in their > address bar and inspect their SSL certificate---but it's important that the > capability is present. Again, the relationship between the restrictions in the license and the restrictions of the product that has been purchased are not straightforward, so it is not clear to me that exposing this information would be useful even to that minority who are interested. In fact, often it might be quite mis-leading. Users can easily judge whether the restrictions being applied match the restrictions advertised, just as they can judge whether the content or the content quality matches what was advertised. It would be like surfacing the bitrate of the first few seconds of the video so that the user can check that they are really getting HD. It just doesn't work because there are many reasons why that bitrate could be less than normal HD bitrates: maybe the first few seconds are mostly blank screens / titles, maybe the first few seconds aren't actually HD because they contain some logo / interstitial but the actual content is HD etc. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 17 October 2014 17:50:16 UTC