17 ms·
WebKit Tracking Prevention Policy
- akersten 7y agoIs there a specific list of the web features that are being restricted? I couldn't find it in the document, and to me pretty much any web feature could be used for fingerprinting. It would be good to have a roadmap for workarounds developers will need to implement to keep legitimate applications working on Webkit.
- om2 7y agoParties that are motivated to do tracking on the web are very creative. Too creative to list every feature they could use. That said, our goal is to as much as possible remove tracking without removing capabilities for non-tracking use cases.
- saagarjha 7y agoAre there plans to list new limitations and why they are being implemented?
- om2 7y agoWe're working on a list of mitigations that we already have in place. We'd try to keep that updated as we add new ones. The main change here is explaining the conceptual reasoning behind our existing mitigations, and how we will decide on future privacy protections.
- saagarjha 7y agoMore explanation of the decision process is a positive in my book :)
- akersten 7y agoI appreciate the efforts, and thanks for replying. My fears are mostly for performant web apps (e.g. games, 60hz+ refresh) where timers are inexplicably inaccurate on one web engine with no documentation explaining why. I hope the restrictions are more subtle, and I understand the desire to keep them somewhat secret this early on.
- om2 7y agoThe limitation on high precision timers isn't due to privacy, it's because of the Spectre/Meltdown family of attacks. We'd like to lift those restrictions, at least conditionally, and are looking into it. I appreciate the note about your use case. (BTW requestAnimationFrame should give you precise callbacks at the screen's refresh rate, and is probably better than using timer-related APIs.)
- akersten 7y agoFundamentally Spectre is a privacy issue, just not in the tracking sense here, right - it's a side channel by which memory can be leaked. Anyway, the reason I brought up timers is that things like getting the screen's refresh rate, or measuring how long a canvas render takes with a particular font, (etc.) are all data points that can be used in a fingerprinting profile. I worry about the negative impacts of mitigations against those kind of measurements. I don't think it's possible to catalog all the various routes by which data could be inferred by timing. If things like this are in the scope of what Webkit is trying to prevent, I'm fairly nervous. Off topic, but just for some game industry perspective: often we don't want to sequence exactly at the refresh rate (especially if it's variable or frames are being dropped) in contexts like logic loops or physics simulations that need to happen at specific frequencies regardless of how quickly frames are drawn. For example, synchronizing a client "tick rate" with a game server's requires millisecond precision.
- om2 7y agoThanks for the info. For dual use technologies we are considering a machine learning approach to identifying fingerprinters (as opposed to legit clients). Also, to my knowledge, screen refresh rate is not currently a top fingerprinting vector. As for Spectre, we treat it primarily as a security threat. It can admittedly be privacy invasive but it would be awkward to use it for tracking.
- zawerf 7y agoI am not caught up on browser engines, but WebKit is mostly just Safari and iOS browsers right?
- saagarjha 7y agoWebKit is also used in a number of other places, such as GNOME Web and browsers for many consoles.
- om2 7y agoIndeed, the Gtk+ and WPE ports, as well as Sony's Windows port, are the most active after the Apple-maintained ones.
- radicaldreamer 7y agoSony's Windows Port?
- om2 7y agoThey maintain a Windows port of WebKit as a reference implementation.
- password4321 7y agoThanks to these comments today I am finally running WebKit on Windows for preliminary Safari compatibility testing purposes. This blog[1] explains how to get Windows builds[2] from the WebKit Build Archives on S3 that require Apple Application Support[3]. [1] https://medium.com/@alSkachkov/how-to-load-the-latest-webkit-on-windows-962a9219c1e1 https://medium.com/@alSkachkov/how-to-load-the-latest-webkit... [2] https://build.webkit.org/builders/Apple%20Win%2010%20Release%20%28Build%29 https://build.webkit.org/builders/Apple%20Win%2010%20Release... [3] 7-zip the iTunes installer to extract & install just AppleApplicationSupport.msi https://www.apple.com/itunes/download/win64 https://www.apple.com/itunes/download/win64
- ytch 7y agothe browser in Steam client also uses webkit
- saagarjha 7y agoActual link to the policy: https://webkit.org/tracking-prevention-policy/ https://webkit.org/tracking-prevention-policy/. One thing that I found interesting was these two quotes: > Our current anti-tracking mitigations in WebKit are applied universally to all websites, or based on algorithmic, on-device classification. > If a party attempts to circumvent our tracking prevention methods, we may add additional restrictions without prior notice. These restrictions may apply universally; to algorithmically classified targets; or to specific parties engaging in circumvention. Is this trying to say that WebKit will now apply restrictions to specific parties that the project feels is circumventing tracking prevention? I'm all for these features, but only if they're applied evenly and in a clear way. The solution to circumvention should be mitigations against bypasses, not selective enforcement :/
- om2 7y agoWe're willing to do specifically targeted mitigations, but only if we have to. So far, nearly everything we've done has been universal or algorithmic. The one exception I know of was to delete tracking data that had already been planted by known circumventers, at the same time as the mitigation to stop anyone else from using that particular hole (HTTPS super cookies). This is in contrast to Mozilla and Edge tracking protections, which are based on block lists to a significant extent. The disconnect.me list is likely to be trustworthy, but ultimately it is manually curated. We've tried to stay away from using lists like that.
- anoncareer0212 7y agoYou're manually curating a specifically targeted mitigation list, but it's non-public. Mozilla/Edge's approach seems preferable, not problematic
- om2 7y agoWe are not presently manually curating a specifically targeted mitigations list. Just saying we might in the future. We did do a one shot rollback of HSTS super cookie abuse in the past, but that’s it.
- pspeter3 7y agoWould "Sign In With Apple" be considered a "Privileged Third Party" if they make sure it works but break other Single Sign On providers as an "Unintended Impact"?
- eridius 7y agoI'm not sure what you mean by this; WebKit Tracking Prevention doesn't break third-party login. Third-party login works by handing a token back to the first party, who then stores it directly and validates it on the backend. After the initial login with the third party, the third party isn't involved anywhere that the browser can see. And the initial login happens in a browser window that's navigated directly to the third party, making them the first party for the login form (and therefore able to access any saved login data from previous logins). In fact, this WebKit Tracking Prevention Policy explicitly states that third-party login is implied consent for the third party to identify the user as having the same identity in these multiple places.
- geofft 7y agoTBH a browser prevents Medium from showing a Google iframe in the top-right corner with "Hi geofft, I know your name is geofft, please click the login button geofft," that would be delightful....
- saagarjha 7y agoI’m not quite sure about this, but I think Safari will prevent cross-site tracking in this case until you interact with the thing.
- the8472 7y agoYou can achieve that with firefox containers or - if you want a bigger hammer - first-party isolation.
- om2 7y agoIf you logged into Medium with that account, then Medium would know, and could tell the I frame. But if you didn’t, then the iframe shouldn’t know your user ID unless you click and allow access, at least in Safari.
- awinter-py 7y agodoes anyone have insight to the webkit governance side of this? is this a case of apple fighting their ads battle against google in upstream FOSS?
- panic 7y agoGoogle hasn't been involved with WebKit since they forked it to create Blink.
- anaisbetts 7y agoIf this tweet is accurate, Apple's choices here are pretty hard to explain as anything but "leverage / abuse mobile phone monopoly to kneecap competitors", especially because nowhere in this document does it actually describe how this makes users' lives better in any concrete, specific way https://mobile.twitter.com/Carnage4Life/status/1161779661644300293 https://mobile.twitter.com/Carnage4Life/status/1161779661644...
- elgenie 7y agoUnfortunately, under the current interpretation of US anti-trust law (thanks Robert Bork!), leveraging monopoly to knee-cap competitors is a-OK if it doesn't directly hurt consumers. The chances of anti-trust law returning to an interpretation that protects competition under the current judiciary are nil.
- scarface74 7y agoHow is Apple blocking an ad network “anticompetitive” when Apple’s only ad platform is within the App Store?
- elgenie 7y agoWell, how does a competitor make money on iOS without giving Apple a 30% cut of app installs and in-app purchases and/or using their ad network?
- scarface74 7y agoSimple, the same way that Spotify, Netflix, Amazon (Kindle), DirecTVNow, Sling, and a bunch of other companies do - force people to pay on their own websites to use the app.... Apple doesn’t have an “ad network”.
- RandomBK 7y agoOnly catch here is that Apple also takes a cut of such subscription revenue if it goes through an app [0]. Individually, I support Apple's decisions around enforcing privacy on the web. However, Apple's decisions when taken as a whole is making it incredibly difficult for a company to generate revenue from iOS users without sharing some of that revenue with Apple. Whether this makes Apple a monolopy I do not know, but it's certainly less clear of a good thing than their privacy efforts. [0] https://www.theguardian.com/technology/2019/mar/13/spotify-claim-apple-30-percent-app-store-commission-unfair-european-commission-complaint https://www.theguardian.com/technology/2019/mar/13/spotify-c...
- 1986 7y agoGiven the definition of cross-site tracking and the note on single-site analytics in Unintended Impacts, is it safe to say this will impact all site analytics tools served by a 3rd party (eg Google Analytics, but really almost all "drop-in" frontend analytics)?
- om2 7y agoDepends on whether these drop-in solutions track cross-site, and whether they strictly limit data collection to the context of the first party site.
- mobjack 7y agoGoogle analytics still works since it uses first party cookies but you lose data on repeat vs new visits. There are ways to make GA work around these limitations, but it requires more work than just dropping it in.
- imbored 7y agoTracking and privacy should be areas where other browsers go after chrome hard.
- rale00 7y agoSo what is going to happen when Apple succeeds in making it impossible to make any money off advertisements shown to iOS users on the web? I'm currently imagining a future where publishers start to just redirect iOS traffic to install their app, where they can actually make money. Good news for the walled garden, I guess?
- andykx 7y agoIt is not impossible to advertise without tracking users.
- peanutz454 7y agoFor some reason people just have an aversion to paying for stuff they use. Facebook's revenue per user is less than 7$, I don't use facebook, but do not mind paying that little for something I use instead of getting tracked wherever I go. Similarly Google's service that I use like gmail and photos are easily worth about 7$ per month. I would pay if they said they will stop tracking me. I don't know about youtube.
- cameronbrown 7y agoYouTube being the only one you've listed that has a premium option. The problem is people will say they'll pay but as soon as the option comes up, they don't.
- therealx 7y agoSure, but YouTube doesn't stop tracking you when you pay.
- tialaramex 7y agoBut what does that mean? YouTube keeps a history list, which I download and periodically reset. If it didn't I would need to add some sort of Firefox add-on that remembered which videos I'd seen. What else are they "tracking"? Does YouTube have tracking on other sites (like Facebook, Twitter etc)? I haven't seen anything like that. You can switch the history off, I presume that would work even without Premium, but it never occurred to me to even try it since I definitely want history.
- jesstaa 7y agoI expect that tracking will just move to being proxied server side. It will be more annoying for the people setting it up but services will spring up to help. Little will change in the advertising and tracking space.
- the8472 7y agoThat annoyance may be enough to keep many actors from just plugging 10 random trackers into their sites, especially when it means running code from less-than-trust-worthy parties on their own servers instead of their user machines. At the very minimum it aligns incentives better for developers to think about these things. And with IPv6 privacy extensions IP addresses will also be less useful for server-side tracking.
- auslander 7y ago> especially when it means running code from less-than-trust-worthy parties on their own servers instead of their user machines. But most will be OK with their servers running Google, Amazon, Oracle BlueKai and Facebook code, the scariest ones by amount of data.
- yyyk 7y ago"IPv6 privacy extensions...." I recall these extensions are just optional. How many implementations actually implement these extensions? I recall Windows 10 had this broken for a year and almost nobody noticed...
- omeid2 7y agoIt is worth reminding that Google Chrome and Chromium no longer use WebKit but Blink. https://www.chromium.org/blink https://www.chromium.org/blink
- winrid 7y agoWow, thanks. Somehow I missed that. Things move so fast.
- Fnoord 7y agoGoogle forked WebKit (itself a fork of KDE Konqueror's KHTML). Blink is from 2013. [1] I wonder how source incompatible these are? Is it difficult to backport? Because KHTML was LGPL the source must remain available. Or is it just that these are API incompatible? https://en.m.wikipedia.org/wiki/Blink_(browser_engine) https://en.m.wikipedia.org/wiki/Blink_(browser_engine)
- jefftk 7y agoAfter the fork both WebKit and Blink were able to delete large amounts of no-longer-shared code. Not half the codebase, but still quite a lot. The fork was a recognition of their having been growing apart for a long time. Both groups still watch each other's changes, but it's very rare that a patch would apply cleanly.
- om2 7y agoIt is still possible to make changes that are mostly reusable for both, but it takes some effort, and some parts (JS engine, multiprocess architecture) are so different that you just have to write it twice.
- randall 7y agoWow, it's been 6 years??? That's surprising.
- _verandaguy 7y ago
- ignoramous 7y agoStrange for a page espousing anti-tracking [0] to load media in from apple.com. Granted Mozilla's page [1] is even a worse offender with google-analytics and newrelic embeds. Really makes you think what really drives the underlying narrative for such initiatives at corporates if not sabotaging competitors? OpenDNS founder, u/davidu, pointed out that DNS over HTTPS, something that takes aim at trackers and advocates privacy, also, in fact, had support of BigAdTech [2]. The content blocker ecosystem has been fighting the dragnet for a long time without expecting anything in return save for examples like Brave and Adblock. It'd be a shame to see those subject to embrace, extend, extinguish. > And we will create new web technologies to re-enable specific non-harmful practices without reintroducing tracking capabilities. I wonder what this means. Another standard that AdTech can rally behind? Or, Apple's way of wrestling control away from AdTech? Remember, not long ago Apple disallowed 3p browsers for a long time, on AppStore...and they are likely going to act as gate-keepers here, as well? > we will typically prioritize user benefits over preserving current website practices. We believe that that is the role of a web browser, also known as the user agent. Where have I heard that before? [3] And now... what about apps on AppStore? When do we get anti-tracking measures there? Pretty soon, would be really great, because that's a present and clear danger, in my eyes, wrt privacy... but one that hurts Apple's bottomline? [0] https://webkit.org/tracking-prevention-policy/ https://webkit.org/tracking-prevention-policy/ [1] https://wiki.mozilla.org/Security/Anti_tracking_policy https://wiki.mozilla.org/Security/Anti_tracking_policy [2] https://news.ycombinator.com/item?id=18257318 https://news.ycombinator.com/item?id=18257318 [3] https://news.ycombinator.com/item?id=20542656 https://news.ycombinator.com/item?id=20542656
- Accacin 7y agoAt least for your second point https://bugzilla.mozilla.org/show_bug.cgi?id=697436#c14 https://bugzilla.mozilla.org/show_bug.cgi?id=697436#c14
- ignoramous 7y agoThanks.
- kitsunesoba 7y ago
- po 7y agoA first party is a website that a user is intentionally and knowingly visiting, as displayed by the URL field of the browser, and the set of resources on the web operated by the same organization. In practice, we consider resources to belong to the same party if they are part of the same registrable domain: a public suffix plus one additional label. Example: site.example, www.site.example, and s.u.b.site.example are all the same party since site.example is their shared registrable domain. A third party is any party that does not fall within the definition of first party above. This policy doesn't distinguish between companies that own multiple top level domains. I understand that it may be technically hard to figure out but at the policy level are two domains owned by one company really third party to each other? Are example.com and example.us really always different first parties? What about apple.com and iCloud.com? Or those redirect chains that happen after logging into google such that login cookies are set on youtube.com and whatnot? It does say 'in practice' but I feel like this is mistaking a technical limitation that it's hard to know if two TLD's are controlled by the same legal entity for a policy.
- om2 7y agoWe have mixed feelings about this. Most people could probably figure out that google.com and google.co.uk are owned by the same entity. And probably many people are aware that youtube.com and google.com are related. But some entities own hundreds of domain names with no clear lexical relationship. I doubt a lot of people would expect TechCrunch.com and huffpost.com to be related and would not really expect to be tracked between the two. So common ownership might not be enough to give users a reasonable expectation of a cross-site relationship.
- tuxone 7y agoAlso, a tracking service could just ask to be CNAMEd to a random subdomain and become everybody’s “first party”, couldn’t it?
- lmkg 7y agoThis has been a feature of Adobe Analytics for over a decade. Google Analytics doesn't currently offer this as a feature, but some enterprising individuals have explored how to hack it in after ITP 2.1 was announced.
- millstone 7y agoJust want to say thanks. I use Safari by choice and feel good about it, and this ongoing effort is part of the reason.
- Vinnl 7y agoOne advantage of Google's dominance and their business model being so reliant on tracking, is that it's become the moat for its competitors: investing energy into tracking protection is a good way for them to gain a competitive advantage over Google, since it's a feature that Google will not be able to copy. So as long as Google's competitors remain in business, we'll probably at least have some alternatives that take privacy seriously.
- inapis 7y agoThat's a very interesting point. But tracking-free services won't really have a major mindshare with the general public because you really can't compete with "free." And there's nothing preventing Google from leveraging Youtube/Gmail/Search to push out other browsers which have tracking protection. Youtube already plays less well with Firefox. Gmail isn't exactly snappy on Safari either.
- Vinnl 7y agoYes, competing with Google is still a main challenge. Still, Apple seems to be managing by providing the browser for free as a value-add when you buy their hardware, and by preventing other browser engines from running on iOS. Mozilla's financial dependence on Google is still a major challenge, which they'll hopefully be able to fix before push comes to shove. Microsoft unfortunately did not seem to be able to financially justify the maintenance of their own engine - though then again, their bet appears to be on Windows integration rather than tracking protection.
- auslander 7y ago> Apple seems to be managing by providing the browser for free Plus @icloud.com email service > Mozilla's financial dependence on Google is still a major challenge, which they'll hopefully be able to fix I honestly do not see how. Sticking to Safari for now.
- rpastuszak 7y ago
- p4bl0 7y agoRelated to the way they classify between first party and third party (based on domain names, with its subdomain being the same party), the Public Suffix list [1] is a resource of great value. It allows to know when subdomains actually refers to different parties (e.g., xxx.github.io is neither the same party as yyy.github.io nor as github.io). [1] https://publicsuffix.org/ https://publicsuffix.org/
- quotemstr 7y agoThe public suffix list is a gross hack. The public-ness of a particular domain level ought to be returned as part of the DNS response instead of being looked up out-of-band.
- p4bl0 7y agoI understand your point, but the problem is that anybody can make their DNS response say whatever they want. And you can't even rely on crypto signatures (e.g. DNSSEC), as the people controlling some DNS records are not necessarily the same as their users. For example, GitHub controls DNS for *.github.io so if they wanted to track people across all GitHub Pages, they could. Also, the Public Suffix list isn't something that needs to be polled every time. It is reasonable for browsers to cache it for several days even.
- quotemstr 7y agoI don't think we'd in practice see people lying one way or the other about a particular name level being "public". If GitHub wants to track people across all *.github.io pages, it can, trivially. It controls the infrastructure, after all.
- jefftk 7y ago> If GitHub wants to track people across all .github.io pages, it can, trivially. It controls the infrastructure, after all.* If WebKit fully implements what they're describing here then GitHub should not be able to use their control of *.github.io to track people across those pages.
- auslander 7y agoThat surveillance economy strongly reminds me Tobacco industry. It was cool and trendy until everyone woke up and regulated it to death, as it should be. GDPR is just the beginning.
- rpastuszak 7y agoThe fact that this makes behavioural targeting even harder makes me very happy. What makes me even more happy is that this helps to eliminate the argument stating that 3p cookies can be replaced with heuristics/non-deterministic targeting. So, instead of assigning resources to just another way of targeting users (e.g. hacks, fingerprinting) a developer/PM can already say that these approaches will be prevented in the exact same way. Any further work in this direction would be pointless. Ideally, we'd put more focus on contextual targeting, which is arguably more useful, significantly less creepy and less dubious from the ethical point of view. I just wish Microsoft moved in the same direction with IE. So far they've been more quiet on that subject than Google. That's wishful thinking, I know.
- wyattjoh 7y agoI only with that with the advent of all these different anti-tracking movements, that there was a clear, documented way for "good faith actors" that require technology like localstorage. We've worked really hard to implement a embedded experience via an iframe, but it's becoming increasingly difficult for our software to walk on egg shells as to not trigger it being labelled as a tracker (as it is definitely not, we only utilize localstorage for storing authentication details). Combine that with the fact that without using cookies, there isn't any way for us to support AMP sites, which often incorrectly labels us as a third party tracker. edit: I do realize that the WebKit Tracking Prevention Policy essentially is a guide of how it works, I'm mostly interested in a "this is how to work within these defined walls to not be flagged as harmful"
- om2 7y agoSounds like we need to expand WebKit's implementation of Storage Access API to cover LocalStorage.
- DiseasedBadger 7y agoGood thing Qt ditched awful WebKit for glorious Chrome. Tracking is "mm mm!" good. It also helps make sure Google's predatory non-compliance and Google-board optimizations continue to spread through all websites. #ThanksQt