Skip to content

[Tag Review] - Expected input/output languages #175

@etiennenoel

Description

@etiennenoel

From: w3ctag/design-reviews#1093 (comment)

This allows the implementation to download any necessary supporting material.

We’re worried about the risks of fingerprinting and excessive disk usage from letting the site select an arbitrary set of languages.

We tentatively believe that local models don’t need to be able to understand or produce languages outside the set that the user understands, and possibly the language the page is written in. That set could be downloaded with the main model without allowing the LanguageModel.create() call to control the download—and potentially fingerprint the user’s browsing history—by picking different expected input and output languages. If we allow a site to use its own language, it could still probe by setting the page’s language differently on each load, but that’s much more visible. Is there a reason we shouldn’t believe this? If so, please add it to the explainer’s alternatives considered.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions