Twitter | Pretraživanje | |
John Wilander
State of cross-site tracking 2020, default settings: • Safari, algorithmic prevention • Firefox, list-based prevention • Edge, list-based prevention • Brave, list-based block • Chrome
Reply Retweet Označi sa "sviđa mi se" More
BrendanEich 18. sij
Odgovor korisniku/ci @johnwilander
Does crawl-time algorithmic count as algorithmic in Brave’s case I your view? I think it should, even though we use lists too.
Reply Retweet Označi sa "sviđa mi se"
John Wilander 18. sij
Odgovor korisniku/ci @BrendanEich
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.
Reply Retweet Označi sa "sviđa mi se"
Nathan Smith 18. sij
Odgovor korisniku/ci @johnwilander
Naïve question: How does list-based prevention differ from list-based block?
Reply Retweet Označi sa "sviđa mi se"
John Wilander 18. sij
Odgovor korisniku/ci @nathansmith
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.
Reply Retweet Označi sa "sviđa mi se"
Patrick 18. sij
Odgovor korisniku/ci @johnwilander
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.
Reply Retweet Označi sa "sviđa mi se"
John Wilander 18. sij
Odgovor korisniku/ci @pmclenithan
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.
Reply Retweet Označi sa "sviđa mi se"
Miguel Morales 18. sij
Odgovor korisniku/ci @johnwilander
Ah yes chrome the only one that remotely cares about publishers
Reply Retweet Označi sa "sviđa mi se"
Priveligiert 18. sij
Odgovor korisniku/ci @therevoltingx @johnwilander
nobody forces publishers to use (excessive) cross site tracking.
Reply Retweet Označi sa "sviđa mi se"
Josep M. Pujol 18. sij
Odgovor korisniku/ci @johnwilander
Cliqz, algorithmic prevention [since 2017] (in case you want to expand the list)
Reply Retweet Označi sa "sviđa mi se"
ℨ𝔞𝔠𝔥 𝔈𝔡𝔴𝔞𝔯𝔡𝔰 18. sij
Odgovor korisniku/ci @johnwilander
Nice thread. Would love to see the same analysis/discussion for the mobile environment & SDK data access 🖖
Reply Retweet Označi sa "sviđa mi se"