-
Notifications
You must be signed in to change notification settings - Fork 18
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
The Topics API #111
Comments
Our analysis of the proposal assumes full per-top-level-site partitioning and no high entropy device fingerprinting such as IP address available cross-site. It’s important that any pre-existing privacy deficiencies on the web not be used as excuses for privacy deficiencies in new specs and proposals. We do not think Topics API is a good addition to the web platform. Here’s why:
As such I suggest we label this "position: oppose" on January 6, giving additional time due to the holidays. |
Closing as we've identified our position. |
Request for position on an emerging web specification
Information about the spec
Design reviews and vendor positions
Anything else we need to know
Feedback was previously requested and given on webkit-dev, but colleagues and I wanted to reproduce it here due to formatting concerns and it generally being useful to have more of our positions here. This also gives others a chance to weigh in if they missed it the first time around.
The text was updated successfully, but these errors were encountered: