Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

privacy concern about connection type and fingerprinting #5

Open
marcoscaceres opened this issue Jan 15, 2014 · 1 comment
Open

privacy concern about connection type and fingerprinting #5

marcoscaceres opened this issue Jan 15, 2014 · 1 comment

Comments

@marcoscaceres
Copy link
Contributor

Quick note: As the type value is shared globally across all documents, it can be used together with other bits of data to fingerprint. Need to document this somewhere.

@marcoscaceres
Copy link
Contributor Author

Elsewhere, @npdoty wrote:

I believe there are two common mitigations of this kind of privacy concern: 1) not firing events for background windows (which works for some APIs, but perhaps not this one if the background loading use case is expected to be particularly important); 2) allowing fuzzing of the event firing by the UA (which seems to be particularly amenable here, as simultaneous event firing or real-time updates of network connectivity are likely not essential).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant