Project

General

Profile

Actions
Copy link

Feature #481

closed

Restrict the definition of third-party to any domain mismatch

Added by Soren Stoutner over 6 years ago. Updated 9 days ago.

Status:
Closed
Priority:
Next Release
Assignee:
Soren Stoutner
Start date:
07/24/2019
Due date:
% Done:

0%

Estimated time:

Description

Currently, any sub domains of the principle domain are not considered third-party domains.

Browsing with all third-party requests disabled breaks so many websites that it is quite difficult to use it as a default settings. Over time, I would like to grow Privacy Browser to the point where it has at least 20% market share world wide. At that point, I intend to make blocking of third-party requests the default behavior. If I have that much market share, web developers will change their methods to make websites work without third-party requests. Also at that point, it would make sense for Privacy Browser to have an a more constricted third-party option that considers any domain that is not an exact match to be a third-party request.

Actions
Copy link
 #1

Updated by Soren Stoutner 9 days ago

  • Priority changed from 4.x to Next Release

I have decided to implement this along with the refactoring of the filter list code. The main motivation in doing so is to bring feature parity with Privacy Browser PC, which requires an exact domain match to not be considered a third-party request.

Actions
Copy link
 #2

Updated by Soren Stoutner 9 days ago

  • Subject changed from Create an option to restrict the definition of third-party to exact domain matches to Create an option to restrict the definition of third-party to exact domain mismatches
Actions
Copy link
 #4

Updated by Soren Stoutner 9 days ago

  • Subject changed from Create an option to restrict the definition of third-party to exact domain mismatches to Restrict the definition of third-party to any domain mismatch
Actions
Copy link

Also available in: Atom PDF