I wrote a blog post about why I insist people use the forums and issue trackers.
“In contrast to more aggressive solutions, Mozilla’s approach simply confines third-party cookies to individual websites rather than blocking them outright.”
I have blocked all third-party cookies for years and it has never caused a single problem.
You don’t want your “private” search engine to have a paid relationship with an upstream non-private search engine for the same reason you don’t want your browser to have a paid relationship with your search engine: Because, sooner or later, that paid relationship will result in tracking.
This is trying to solve a problem that doesn’t exist. The only attribution that advertisers need is to track the number of hits their server sees on the URLs in their ads. If they see a lot of hits, then the ad campaign is working. I can’t imagine any world where it would be a good idea for advertisers to get any more information than that.
With the publication of the Privacy Browser PC Git repository, the URLs for Privacy Browser Android have been updated to reflect the difference between the two.
The codebase for Privacy Browser PC has been posted online. Currently it doesn’t do much, but I would expect development to progress quickly.
Among other things, it increases the attack surface of the browser, making bugs in other things (like Safari’s buggy IndexedDB implementation) exploitable.
And the core reason why the browser market is ripe for disruption is because all the major browsers currently make their money by monetizing the search engine. Which means that they don’t make decisions in the best interests of users.
The browser market is ripe for disruption.
I am the principal developer of Privacy Browser, a web browser that respects your privacy.
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.