Disabling third-party cookies hasn't really been that useful in a long time though.

"When third-party cookies are allowed, 101 domains can reconstruct over 50% of a user's history and 161 could recover over 40%. Even when these cookies are blocked, 44 domains could recover over 40% of a user's history."[1]

[1] Study back in 2014: https://securehomes.esat.kuleuven.be/~gacar/persistent/the_w...

Add to that web beacons, ads, like buttons, browser fingerprinting via HTTP header, javascript, canvas, plug-ins, add-ons or hardware, keystroke biometrics and gestures on smartphones. Of course, there are also several techniques for e-mail tracking as well as tracking of documents (word, .pdfs etc).

Thankfully this became the default in Safari: https://webkit.org/blog/10218/full-third-party-cookie-blocki...

Previously it only enabled third-party cookies for domains you had explicitly visited. https://www.theverge.com/2017/9/14/16308138/apple-safari-11-...

Unfortunately, people are working out ways to get around this now that it's become a default.

Use a generic JS blocker. It protects you from workarounds and zero days.

It also blocks JS.

You say that like it's a bad thing?

Doesn't stop tracking pixels.

If you use umatrix and only allow 1st party cookies it should block those right? The pixel would load but without any cookie.

Tracking pixels don't need a cookie if they're using dynamically generated URLs.

umatrix can block third-party images as easily as it blocks cookies.