Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Smart Tracking Protection #539

Open
tomlowenthal opened this issue Jul 13, 2018 · 2 comments
Open

Smart Tracking Protection #539

tomlowenthal opened this issue Jul 13, 2018 · 2 comments

Comments

@tomlowenthal
Copy link
Member

@tomlowenthal tomlowenthal commented Jul 13, 2018

We should intelligently block unexpected tracking by avoiding state from origins the user isn't trying to visit. Safari has a similar feature: https://webkit.org/blog/8311/intelligent-tracking-prevention-2-0/

Replaces brave/browser-laptop#10983


Here are the sub-tasks for this project so far:

@bbondy bbondy added this to the Backlog milestone Jul 26, 2018
@tomlowenthal tomlowenthal mentioned this issue Aug 22, 2018
0 of 2 tasks complete
@tomlowenthal tomlowenthal changed the title Smart Tracking Protection Smart Tracking Protection [overall feature] Aug 22, 2018
@jumde jumde added this to Untriaged / Incoming in Shields Nov 15, 2018
@tomlowenthal tomlowenthal moved this from Untriaged / Incoming to Feature Backlog in Shields Nov 27, 2018
@rebron rebron modified the milestone: 1.x Backlog Feb 7, 2019
@tomlowenthal tomlowenthal added the Epic label Jul 10, 2019
@tomlowenthal tomlowenthal changed the title Smart Tracking Protection [overall feature] Smart Tracking Protection Aug 5, 2019
@ghost
Copy link

@ghost ghost commented Dec 12, 2019

Lots of updates since that initial post: https://webkit.org/blog/category/privacy/

https://webkit.org/blog/9661/preventing-tracking-prevention-tracking/ new tidbits that webkit has implemented to prevent sites from tracking the prevention of tracking. interestingly, google is helping them design it.

  • Origin-Only Referrer For All Third-Party Requests
  • All Third-Party Cookies Blocked on Websites Without Prior User Interaction
  • The Storage Access API Takes the Underlying Cookie Policy Into Consideration
  • Absence of Cookies In Third-Party Requests Does Not Reveal ITP Status
@pes10k
Copy link
Contributor

@pes10k pes10k commented Dec 12, 2019

FWIW, Google is most def not helping them design it. Google was exploiting a bug that would bypass, WebKit folks noticed it and plugged the hole. The comment is shade 😎

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Shields
  
Feature Backlog
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.