3 ms·
Couldn't read all of it due to paywall. What is technically happening with these features? As far as I understand it, there is a cookie that lives in the brows
by fareesh 9y ago
Couldn't read all of it due to paywall.
What is technically happening with these features? As far as I understand it, there is a cookie that lives in the browser which gets sent with the request to the Google/Facebook ad script CDN, or an iframe reads the browser's cookies.
Is Safari running some kind of Machine learning or other algorithm that guesses which cookies are hurting privacy and which ones aren't, and expires them sooner compared to other cookies?
What are the odds that safari ends up breaking some other cookie driven functionality ? Can google theoretically use an iframe that reads localstorage instead? Websql?
Can't Facebook still use the like button to track users? Or does this change mean having to sign in to like things.
I feel like this is not possible to fix without breaking persistent storage for the web. Maybe I am missing something. There are a lot of use cases where I might need this. SSO for multiple domains is one that immediately comes to mind.
I think that the current approach of private browsing mode which puts the user in charge is good enough from a privacy standpoint.
- Terretta 9y agoAnswers to many of your questions here: https://webkit.org/blog/7675/intelligent-tracking-prevention/ https://webkit.org/blog/7675/intelligent-tracking-prevention...