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.

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

Positions on the standards Webkit considers to be vulnerable to fingerprinting #378

voxpelli opened this issue Jun 29, 2020 · 2 comments


Copy link

voxpelli commented Jun 29, 2020

The WebKit team recently published a list of standards which they refrain from implementing in their current state due to fingerprinting concerns.

Of those at least 5 already have public positions from you:

But the rest are missing such as far as I can see:

As this blog post has caused some discussion on eg. Twitter, it would be interesting to know more about your position on more of those that the WebKit team are skeptical towards. Maybe you agree with them and find all of them harmful or maybe there are some which you actually think differently about.

Sorry if this is a much too wide request. I think it's better to open this and have it closed by you and then to know that you think it's a too wide question than not to ask. I hope that is okay with you 🙏

Copy link

saulamsal commented Jun 30, 2020

Would love to know if Mozilla has any consideration regarding Network Information. Serving different resources based on network information and adjusting the content will greatly benefit PWAs.

Copy link

dbaron commented Jun 30, 2020

So I think having a single issue for multiple requests for positions will quickly become impractical: too difficult to follow and track. So I think we should stick to our general policy of having one issue per specification on which a position is requested.

I've edited your initial comment to link to the existing issues on these specifications -- some of the "missing" ones have open issues, some with a good bit of discussion so far -- although a number also don't have issues that I could find.

(I think there are also some of those where we've publicly stated positions prior to the existence of this repository but never documented here, and also some of those that we haven't really analyzed yet.)

@dbaron dbaron closed this as completed Jun 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

No branches or pull requests

3 participants