- From: Harald Alvestrand <harald@alvestrand.no>
- Date: Thu, 06 Dec 2012 09:03:24 +0100
- To: public-media-capture@w3.org
On 12/06/2012 01:28 AM, Martin Thomson wrote: > On 5 December 2012 16:10, Cullen Jennings (fluffy) <fluffy@cisco.com> wrote: >> I don't think that removing mandatory constraitns is going to work because that means you can't tell the app can't work until the user is already into a call and that is a pretty terrible UX. > That presumes a conclusion to the fingerprinting issue that results in > all capabilities being exposed to applications. I'm sympathetic to > that viewpoint, but I hadn't quite made that leap yet. > One mitigation strategy we discussed briefly in Lyon was to make failure on unsatisfied constraints rate-limited - that the callback would return more slowly the second/third/fourth time a constraint failed. This would sharply limit the bandwidth of the fingerprinting channel.
Received on Thursday, 6 December 2012 08:05:08 UTC