Feature #481
openCreate an option to restrict the definition of third-party to exact domain matches
0%
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.
No data to display