Script Blocking Exceptions Update
We have received many questions about script blocking exceptions being reported by several news outlets and blogs. This conversation is about script loading, not tracking. Loading a script from an edge-cache does not track a user without third-party cookies or equivalent browser-local storage, which Brave always blocks and always will block. In other words, sending requests and receiving responses without cookies or other means of identifying users does not necessarily create a tracking threat.
Brave aims to maintain a working Web, while reducing or eliminating the invasive tracking that has become so ubiquitous online. In order to do this, we make the conventional distinction between first-party and third-party content, granting different permissions to each.
First parties are the websites you’re directly accessing, whereas third parties are embedded widgets and other resources in the page, which are indirectly accessed. If a user navigates to a website, they may find that several other requests will be made to fetch resources on other websites. Depending on the website, Brave may cancel the request entirely, or permit it while severely limiting access to user data.
We found that blocking certain third-party scripts broke many sites, so predicated on our cookie blocking and fingerprinting protection, we hardcoded some exceptions to ensure the best possible user experience. For example, Facebook and Twitter both contain widgets which web authors can integrate into their online properties. These widgets aim to make it easier for users and publishers to connect by allowing users to authenticate through Facebook or Twitter, rather than creating and maintaining an account with the publisher themselves. The exception list covered by several news outlets allows both of these widget sets to operate on a leash. They can load, but they cannot access local data on the client so as to track the user.
For many publisher implementations, blocking the script request would break Facebook-based OAUTH and Facebook likes and shares.
Fingerprinting is not always a reliable tracking method.
At Brave, we continually work to protect users without breaking the Web and users can always be assured that we are doing everything in our power to prevent third-parties from eavesdropping on their browsing experience. We are working to eliminate these script-blocking exceptions without blocking the embedded widgets with which some users do choose to interact.
Continue reading for news on ad blocking, features, performance, privacy and Basic Attention Token related announcements.
At Brave, we want to make crypto usable and defi accessible for everyone, and towards that end we are excited to share the progress we have made since we published the BAT Roadmap 2.0 in February 2021.
Brave Today, the privacy-preserving news reader integrated into the Brave browser, now features RSS feeds for users. This option is available today with Brave’s iOS app update (v1.24), and coming soon to the Brave desktop browser.
Capitalizing on our user base and the success we have had with BAT adoption, we intend to make crypto and decentralized finance (DeFi) accessible and usable for everyone through the following efforts.
This post presents “ephemeral site storage”, a new strategy for managing third-party storage in Brave, designed to improve Web compatibility, while maintaining the same level of privacy protection.
The Brave Today news reader is accessible below the new tab page and is delivered anonymously to the user’s browser via Brave’s new private content delivery network.
Brave is a company where privacy isn’t just a feature; it’s a requirement. This is perhaps most obvious in the Brave Browser, where we block trackers, prevent fingerprinting, and include a privacy-preserving, opt-in and user-first ad-system, but Brave’s focus on privacy goes far beyond the browser.