|
@johnwilander | |||||
|
State of cross-site tracking 2020, default settings:
• Safari, algorithmic prevention
• Firefox, list-based prevention
• Edge, list-based prevention
• Brave, list-based block
• Chrome
|
||||||
|
||||||
|
BrendanEich
@BrendanEich
|
18. sij |
|
Does crawl-time algorithmic count as algorithmic in Brave’s case I your view? I think it should, even though we use lists too.
|
||
|
|
||
|
John Wilander
@johnwilander
|
18. sij |
|
Not in my view. This is about the browser. If it ships with a list that the vendor can look at and that the vendor can decide which things go on or off it, it’s list-based. I assume all list creators/vendors do some kind of crawling with algorithms tied to it.
|
||
|
|
||
|
Nathan Smith
@nathansmith
|
18. sij |
|
Naïve question:
How does list-based prevention differ from list-based block?
|
||
|
|
||
|
John Wilander
@johnwilander
|
18. sij |
|
Not naïve at all. 🙂 Prevention typically means stopping the means of tracking (cookies etc) while still allowing the resource loads. Blocking typically means blocking loads, as in content blockers and af blockers.
|
||
|
|
||
|
Patrick
@pmclenithan
|
18. sij |
|
It be nice if browsers just offered transparency to the user and developers instead of selling "trust". It's a difference between teaching the user and "protecting" the user. Giving my opinion respectfully, I know it's not a popular one right now.
|
||
|
|
||
|
John Wilander
@johnwilander
|
18. sij |
|
I think we’re super transparent. We blog about all changes to our tracking prevention and those blogposts go through review to make them approachable. The whole implementation is open source. And we have a public tracking prevention policy that guides us going forward.
|
||
|
|
||
|
Miguel Morales
@therevoltingx
|
18. sij |
|
Ah yes chrome the only one that remotely cares about publishers
|
||
|
|
||
|
Priveligiert
@priveligiert
|
18. sij |
|
nobody forces publishers to use (excessive) cross site tracking.
|
||
|
|
||
|
Josep M. Pujol
@solso
|
18. sij |
|
Cliqz, algorithmic prevention [since 2017] (in case you want to expand the list)
|
||
|
|
||
|
ℨ𝔞𝔠𝔥 𝔈𝔡𝔴𝔞𝔯𝔡𝔰
@thezedwards
|
18. sij |
|
Nice thread. Would love to see the same analysis/discussion for the mobile environment & SDK data access 🖖
|
||
|
|
||