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.
Brave and UC San Diego Announce SugarCoat, A New Solution to Strengthen the Protection of Web Users’ Privacy While Not Breaking Websites
Brave is pleased to announce SugarCoat, the result of a year-long research collaboration with University of California San Diego to create a new system to improve Web privacy without sacrificing compatibility at Web scale.
Today, we launch the Brave Wallet, a native wallet built into the browser, enabling users to store, manage, grow, and swap crypto from within Brave.
Brave partners with Solana to integrate it into the browser and make it the default for DApp support
Brave will integrate the Solana blockchain, providing default Solana ecosystem support to Brave’s 42 million MAUs and 1.3 million verified Creators.
Starting today, new Brave users will have the search functionality in the Brave browser powered by Brave Search, giving them the privacy and independence of a search/browser alternative to Big Tech.
This is the eleventh post in an ongoing, regular series describing new privacy features in Brave. This post describes work done by Senior Software Engineer Mark Pilgrim and Filter List Engineer Ryan Brown, and was written by Director of Privacy Peter Snyder.
Today, Brave launched Brave Talk, a new privacy-focused video conferencing feature built directly into the Brave browser.