Skip to content

Improve the Privacy and Security section. #42

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

Merged
merged 3 commits into from
Dec 3, 2020

Conversation

darktears
Copy link
Contributor

@darktears darktears commented Nov 17, 2020

Closes #???

The following tasks have been completed:

  • Modified Web platform tests (link to pull request)

Implementation commitment:


Preview | Diff

@darktears
Copy link
Contributor Author

@anssiko @kenchris @diekus-zz PTAL

index.html Outdated
for browser fingerprinting, in a way that can help fully or partially
identify individual users. It is up to the implementer to minimize this,
and some proposed solutions are listed below.
The Screen Fold API exposes two types of information:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

kinds of ?

index.html Outdated
The Screen Fold API exposes two types of information:
<ol class="algorithm">
<li>
an |angle| value coming from the hinge position
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

representing the

index.html Outdated
an |angle| value coming from the hinge position
</li>
<li>
A |posture| determined from the angle value
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

|angle| so that it links to the above?

@anssiko
Copy link
Member

anssiko commented Nov 17, 2020

PTAL @diekus

index.html Outdated
However the fold angle only communicates its value when the hinge is manipulated by the user.
Variations in the angle’s readings and posture calculation, as well as event dispatching frequency
offer a possibility of fingerprinting to identify users. User agents may reduce this risk by limiting
or coalishing events when exposing this information to web developers. Users don’t constantly adjust
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

coalescing

@darktears
Copy link
Contributor Author

Thanks @anssiko. Feel free to merge whenever you'd like.

@darktears
Copy link
Contributor Author

@lauramorinigo any feedback?

@anssiko
Copy link
Member

anssiko commented Dec 3, 2020

@darktears I’ll let @kenchris merge when he’s happy. LGTM.

Any further feedback we can incorporate in updates. This is a good first stab.

@kenchris kenchris merged commit f8db538 into w3c:master Dec 3, 2020
@LaszloGombos
Copy link
Member

This mitigation looks good to me. Thanks !

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

Successfully merging this pull request may close these issues.

4 participants