Skip to content

Wordsmithing for 2025 #69

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 1 commit into from
Mar 20, 2025

Conversation

tomrittervg
Copy link
Contributor

@tomrittervg tomrittervg commented Jan 17, 2025

Addresses #68

Some of these changes are more syntactic than semantic, I tried to limit those but a few still jumped out to me.


Preview | Diff

@tomrittervg tomrittervg force-pushed the 2025-01-17-tjr-wordsmithing branch from 37049b7 to a5bdb3d Compare January 28, 2025 16:27
Copy link
Contributor

@npdoty npdoty left a comment

Choose a reason for hiding this comment

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

Good updates and improvements, thanks!

Copy link
Member

@jyasskin jyasskin left a comment

Choose a reason for hiding this comment

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

2 nits and a note:

Permanent identifiers or other state (for example, identifiers or keys set in hardware) should typically not be exposed. Where necessary, access to such identifiers would require user permission (however, explaining the implications of such permission to users may be difficult) and limitation to a particular origin (however, server-side collusion between origins will be difficult to detect).
As a result, your design should not rely on saving and later querying data on the client beyond a user's clearing cookies or other local state. That is, you should not expect any local state information to be permanent or to persist longer than other local state.
Permanent identifiers or other state (for example, identifiers or keys set in hardware) should typically not be used. Where necessary, access to such identifiers would require user permission and limitation to a particular origin. However even heavy-weight mitigations are imperfect: explaining the implications of such permission to users may be difficult and server-side collusion between origins is typically impossible to detect.
As a result, your design should not rely on saving and later querying data on the client and expecting it to persist beyond a user clearing cookies or other local state. That is, you should not expect any local state information to be permanent or to persist longer than other local state.
Copy link
Member

Choose a reason for hiding this comment

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

No particular change needed in this PR, but we do have features that encourage some local state to persist longer than other state. Passwords in the password manager, especially, but also https://storage.spec.whatwg.org/#dom-storagemanager-persist and https://github.com/WICG/storage-buckets/blob/main/explainer.md help websites give different lifetimes to different state, and I think that's all consistent with privacy.

@tomrittervg tomrittervg force-pushed the 2025-01-17-tjr-wordsmithing branch from d629e5f to ecd1704 Compare February 13, 2025 21:27
 - Strengthing wording to describe fingerprinting as a threat
 - Mentioning VPNs as a common privacy tool that does not help
 - Stripping mentions of plugins.
 - Mention advances in CSS-based fingerprinting
 - Mention the differences between client-side fingerprint calculation and server-side
 - Mention User Gesture
 - Various other small wordsmiths
@tomrittervg tomrittervg force-pushed the 2025-01-17-tjr-wordsmithing branch from ecd1704 to 6db14f6 Compare March 20, 2025 13:50
@tomrittervg
Copy link
Contributor Author

Rebased

@npdoty npdoty merged commit f7c5f77 into w3c:gh-pages Mar 20, 2025
1 check passed
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