Nick Doty

WICG/media-capabilities#28 has been closed, but I don't see an explanation of the conclusion. Is this issue still relevant on this spec or is the discussion to be moved elsewhere? I'm...

Is the suggestion that MediaStream Recording is going to incorporate the Media Capabilities draft community group report to require implementation of the `mediaCapabilities` attribute? Or that MediaStream Recording will continue...

@yellowdoge that makes sense. I'll open separate issues re: fingerprinting on Media Capabilities. I understand wanting to delegate the capabilities functionality, which I think would be a good reason to...

@guest271314 feel free to add to issue #142 if you have comments on the privacy impacts of `isTypeSupported`. As noted in that issue, it's possible that the surface exposed in...

If the data returned by `isTypeSupported` won't vary between implementations, or there's some assurance that a particular OS/UA implementation won't have variations inside of it, then that would affect the...

Currently, the first example in the specification demonstrates how to enumerate the list of supported codec/container combinations in the user's browser: https://w3c.github.io/mediacapture-record/#example1 I don't think you want to recommend doing...

> Those are informational for developers but they are not offered to the JS, i.e. a hardware accelerated version is only supported if and where there's a software fallback, and...

It seems trivial to conceive of `isTypeSupported` providing more information than the user agent vendor: for example, if an implementer made support of different types dependent on the underlying codecs...

For those who feel any concern about "privacy" is nonsensical, it's likely that issues raised in a privacy review may not be of interest. It may not be worth our...

Sure. The section seems especially brief. Have the editors or the group gone through the security questionnaire as described in #122? * Are there no privacy or security implications beyond...