[om2]

We have a partial mitigation and it does not involve stripping query params.

We'll be doing more stuff in standards first / in parallel now that more browsers are actively engaged in reducing tracking.

A lot of the more extreme thing we'll only do for sites that we've classified as a tracker. Other browsers put identified trackers in all kinds of penalty boxes that aren't fully defined by standards yet. (We happen to do the identification using machine learning instead of a curated block list.)

[ec109685]

I guess this is what the article’s main point — putting sites on notice that no matter how much they obfuscate their cross-site linking practices, WebKit can always hard code mitigation’s for that site.

If social.example links to blog.example, limit cookie storage to 24 hours, no matter what is in the link.