Changing Our Approach to Anti-Tracking

Re:Changing Our Approach to Anti-Tracking by bsdubernerd on Thursday August 30, 2018 @10:47AM (#17877165)

I've been blocking 3rd-party cookies since a decade now. I have never witnessed any website breaking. And I do regularly buy from online shops (ebay, amazon, lots of others) while blocking 3rd-party cookies.

I'd really want to know which websites do break, and if they do, in which fashion.

[ Parent | on HN ]

Re:Changing Our Approach to Anti-Tracking by sammacbeth_ on Thursday August 30, 2018 @11:09AM (#17877358)

Here are some examples: https://whotracks.me/blog/block-third-party-cookies.html

[ Parent | on HN ]

Re:Changing Our Approach to Anti-Tracking by jmspring on Thursday August 30, 2018 @10:49AM (#17877184)

I’ve had online bill pay sites - typically banks - fail with some tracker blocking enabled.

[ Parent | on HN ]

Re:Changing Our Approach to Anti-Tracking by jiveturkey on Thursday August 30, 2018 @01:24PM (#17878651)

same. those all work for me now, though, since maybe 1 year ago.

[ Parent | on HN ]

Re:Changing Our Approach to Anti-Tracking by KajMagnus on Friday August 31, 2018 @11:00AM (#17886104)

Maybe this one? Embedded comments in an iframe, and if you login, there'll be a session cookie, in the iframe. There's no tracking — each blog has its own unique sub domain with unique cookies, and no cookies on the 2nd level domain. Still, disabling 3rd party cookies in Chrome seems to break login:

https://www.kajmagnus.blog/new-embedded-comments

(what happens if you try to post a comment. I think there'll be an error. I'm developing this b.t.w.)

[ Parent | on HN ]

Re:Changing Our Approach to Anti-Tracking by TheRealPomax on Thursday August 30, 2018 @11:40AM (#17877598)

The immediate thought is "sites that rely on content being discussable" through things like disqus and the like (mostly because that covers one of my websites). The third party cookies allow for off-site autologins. Of course, allowing them also lets BS like facebook in so I'd love to see browser get built-in automatic third-party blocking with per-site whitelisting of 3rd party domains (I would love to auto-clear disqus on sites I actively use, but not on sites that happen to have it slapped onto a random 1 paragraph "news" item).

[ Parent | on HN ]

Re:Changing Our Approach to Anti-Tracking by welder on Thursday August 30, 2018 @06:39PM (#17881426)

They fix this by opening a new window and having you login directly to Disqus.com so the cookie can be set. Disqus login still works with third-party cookies disabled...

However, don't use Disqus because they inject vulnerable JavaScript onto the page from unvetted ad networks and inject their affiliate links into every external link on your page[1].

[1]: https://en.wikipedia.org/wiki/Disqus#Affiliate_links_and_thi...

[ Parent | on HN ]

Re:Changing Our Approach to Anti-Tracking by joemccall86 on Thursday August 30, 2018 @11:38AM (#17877574)

Google Meet would basically not work for me until I enabled third-party cookies. Nobody could hear my audio.

[ Parent | on HN ]

Re:Changing Our Approach to Anti-Tracking by Mithriil on Thursday August 30, 2018 @11:21AM (#17877441)

Do you use an add-on to block cookies? If not, how?

[ Parent | on HN ]

Re:Changing Our Approach to Anti-Tracking by coolspot on Thursday August 30, 2018 @11:40AM (#17877596)

I also recommend Cookie AutoDelete for firefox[1] and Chrome[2].

1 - https://addons.mozilla.org/en-US/firefox/addon/cookie-autode...

2 - https://chrome.google.com/webstore/detail/cookie-autodelete/...

[ Parent | on HN ]

Re:Changing Our Approach to Anti-Tracking by crtasm on Thursday August 30, 2018 @11:32AM (#17877534)

Firefox has an option for allowing third party cookies: always/from visited/never.

[ Parent | on HN ]