3 ms·
> I quickly googled this for you, found this Right, "1292 days ago". Now that we've just talked about information that is out-of-date. > Blocking 3rd party co
by marco1 10y ago
> I quickly googled this for you, found this
Right, "1292 days ago". Now that we've just talked about information that is out-of-date.
> Blocking 3rd party cookies breaks surprisingly few things
Agreed. A comment from the post that you linked to.
Disqus being one of the few exceptions that don't work (because it's embedded as a third-party on first-party sites), personally, I can live with that. Everybody has to decide for themselves. If some setting doesn't work, it can simply be undone.
- dao- 10y ago> Disqus being one of the few exceptions that don't work (because it's embedded as a third-party on first-party sites), Just like e.g. Facebook Login and github accounts, right? > personally, I can live with that. Everybody has to decide for themselves. If some setting doesn't work, it can simply be undone. Except that the list that you promoted here has no detailed documentation and doesn't put users in the position to make an informed decision.
- marco1 10y agoFacebook login, Google login, etc. still work (at least with most implementations), since they redirect to the SSO site, which is what every reasonable site should do, instead of using an iframe/embed. Good luck finding something that considerably improves your privacy while breaking 0.000% of modern sites.
- dao- 10y agoI'm not blaming you for the fact that disabling third-party cookies may break some sites. The problem is that you provided a long list of preferences privacy-sensitive users allegedly should set, without explaining what these prefs do let alone warning about the possible negative impact.