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.

Sign up for GitHub

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

Jump to bottom

do we cover precision of measurements? (e.g. battery api) #3

Closed
npdoty opened this issue Oct 29, 2015 · 2 comments
Closed

do we cover precision of measurements? (e.g. battery api) #3

npdoty opened this issue Oct 29, 2015 · 2 comments
Labels
pending-review

Comments

@npdoty
Copy link
Collaborator

npdoty commented Oct 29, 2015

It's been pointed out that the Battery API can be used for fingerprinting. Add reference re: https://eprint.iacr.org/2015/616.pdf

Does current guidance sufficiently call out precision of information returned (see data minimization)? Following the guidance in this document should help spec authors to avoid problems like this one.

(Issue via Dave Singer, @englehardt and others.)
@npdoty
Copy link
Collaborator Author

npdoty commented Oct 29, 2015

Also noted by Dom, Frederick and others. See: https://lists.w3.org/Archives/Public/public-privacy/2015JulSep/0038.html

@npdoty
Copy link
Collaborator Author

npdoty commented Oct 29, 2015

Suggested text from Frederick, either for this document or the questionnaire/privacy considerations:

Implementations should ensure that the precision of information is at the lowest accuracy as possible while providing utility.

https://lists.w3.org/Archives/Public/public-privacy/2015JulSep/0039.html

npdoty added a commit that referenced this issue Jul 28, 2016
@npdoty
* "browser fingerprinting" in title, per #5
7970948 
* describe minimization and data precision, including battery and proximity examples, per #3
* fixed wording issue ("provides"), per #4
* added more examples, per #6
* clarifications regarding scope and reference to other portions of the stack, #7
@npdoty npdoty closed this as completed Jan 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
pending-review
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@npdoty