Skip to content

Principles: Reference "Privacy Anti-Patterns in Standards" #91

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

Open
AmeliaBR opened this issue Jun 25, 2019 · 3 comments
Open

Principles: Reference "Privacy Anti-Patterns in Standards" #91

AmeliaBR opened this issue Jun 25, 2019 · 3 comments
Labels
discussion: cost-benefit tags all aspects of the priorities sections and cost-benefit tags section: principles The "Guiding Principles" section, including the tag definitions. status: suggestion this issue discusses a suggested addition to the report, that is not yet in the draft

Comments

@AmeliaBR
Copy link
Member

The recently-published Privacy Anti-Patterns in Standards report from W3C PING should be added to the list of references for the privacy & security part of the Guiding Principles.

I can add the reference, but I'm filing this as an issue to remind other people to read the report! We may want to use its recommendations for additional "tags" for summarizing conclusions on individual capabilities.

@AmeliaBR AmeliaBR added discussion: cost-benefit tags all aspects of the priorities sections and cost-benefit tags status: suggestion this issue discusses a suggested addition to the report, that is not yet in the draft section: principles The "Guiding Principles" section, including the tag definitions. labels Jun 25, 2019
@AmeliaBR
Copy link
Member Author

Another interesting reference: Report from W3C Workshop on Permissions and User Consent (Sept 2018)

@AmeliaBR
Copy link
Member Author

Another reference from the W3 blog, about permission prompts: https://www.w3.org/blog/2019/07/adding-another-permission/

Especially noteworthy is a mention of something that Peter and I have discussed: many uses of geolocation could be better served by a more shielded location feature.

For example, we could design a "location picker" rather than a geolocation permission. User agents could implement an input type where the user selects either her current location or a named location that she has saved and often wants to search about.

@Malvoz Malvoz mentioned this issue May 17, 2021
@Malvoz
Copy link
Member

Malvoz commented Aug 5, 2021

Another reference, about mitigating fingerprinting: https://www.w3.org/TR/fingerprinting-guidance/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion: cost-benefit tags all aspects of the priorities sections and cost-benefit tags section: principles The "Guiding Principles" section, including the tag definitions. status: suggestion this issue discusses a suggested addition to the report, that is not yet in the draft
Projects
None yet
Development

No branches or pull requests

2 participants