Skip to content

Suggestions on improvements for the privacy considerations section #233

Open
@jonathanKingston

Description

@jonathanKingston
  • A line “Underlying codecs are often implemented entirely in software” seems misleading given our findings.
  • It’s unclear to me how a privacy budget would be implemented without impacting web compatibility.
  • In the media capabilities draft they mention how a user agent would provide a subset of features that were common across devices to reduce entropy. This draft should mention the same and it’s not clear where this would go due to the configurations being part of other specifications linked in the codec registry.
  • The Media Capture specification is much clearer about the ability to fingerprint this draft should have all the same pieces.
    • Add sections like this spec to make it easier to read individual topics.
  • No mention of codec output being uniquely identifying.
    • It’s unclear if the output fingerprinting technique is different to the Media Capture specification but as support for more codec capabilities and input types increase (MediaCapture only supports streams) prevention of this using applying noise will become more difficult.

Metadata

Metadata

Assignees

No one assigned

    Labels

    editorialchanges to wording, grammar, etc that don't modify the intended behaviorprivacy-needs-resolutionIssue the Privacy Group has raised and looks for a response on.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions