Update Brave Browser release info


Level 62
Mar 29, 2018
Here's what some of you have been waiting for:

What’s Brave Done For My Privacy Lately? Episode #10: Custom Filter List Subscriptions
Starting in version 1.31.x, Brave will support custom filter list subscriptions, allowing users to further control how unwanted network requests and in-page elements are blocked in Brave. Previously, Brave users could only make selections from the 45 optional regional and special-purpose filter lists Brave included, but now Brave users can subscribe to any filter lists they wish, including the fantastic range of lists maintained by a range of communities, developers and privacy advocates. This work is part of Brave’s goal of providing best-of-breed content filtering tools, and keeping people in control of their Web browsing.

Brave has always provided users with a powerful native content-blocking engine, and shipped a robust set of default filter lists sourced from the excellent work of the Easylist, Easyprivacy, and uBlock Origin list maintainers. Additionally, advanced users have had the option of further customizing their view of the web using the regional and custom filter lists in the brave://adblock settings page. Going forward users can subscribe to any ABP-style filter lists on the internet, allowing them to receive updates from trusted community sources. Any active filter list subscriptions will automatically be updated on a recurring basis, keeping users up to date with the latest privacy protections and website optimizations provided by the list maintainers.

The addition of custom filter list subscriptions brings Brave to parity with other blocking tools like uBlock Origin, AdblockPlus, and AdGuard. This upgrade allows users to further customize their browsing experience natively in the browser without requiring any extensions to be installed. This feature is completely optional; Brave still brings state-of-the-art privacy protections out-of-the-box to millions of users without requiring any additional tweaking.

Custom filter list subscriptions are managed in the brave://adblock page, available on both Desktop and Android. On Desktop, the page can also be accessed through the “Brave Ad Block” menu in the top-right browser hamburger menu, or by right clicking on any page and selecting “Brave > Manage custom filters”. The new section is located directly below Brave’s existing selection of additional regional and special-purpose filter lists.


Users can enter the URL of an online filter list using the “Add filter list via URL” button. Once corresponding URLs are added, subscriptions will appear in a list displaying their URL, time of last local update, as well as controls to temporarily disable the subscription, force an immediate update, view the locally cached version, or unsubscribe.


Active subscriptions will be automatically updated in the background every week. Disabling a subscription will cause its updates to be paused until it is re-enabled. Any subscription can also be manually updated at any time.

Brave’s recent eTLD+1 blocking policy update affects default lists that ship with the browser, aiming to provide an experience where most users never have to deal with web compatibility issues by “dropping Shields.” However, any user-selected lists, including those added through subscriptions, are unaffected by the policy, giving the most advanced users full control over their browsing experience.

You can already try adding some custom subscriptions in 1.31.x today, but be on the lookout for further improvements including better UI for the brave://adblock page, tighter integration with the rest of the browser settings, and some significant performance improvements for users who prefer to enable several filter lists.


Level 75
Content Creator
Malware Hunter
Aug 17, 2014

Release Channel 1.30.86​

Full Release Notes:
  • Added the ability for Brave to handle searches from Windows Shell and Cortana. (#13875)
  • Added “Index other search engines” setting under brave://settings/search. (#14496)
  • Added the ability to disable Tor via Admin policy on macOS and Linux. (#17530)
  • Added the ability to right click in brave://rewards-internals logs. (#16915)
  • [Security] Added IPFS gateway URL validation. (#16999)
  • Improved “Disconnected” Brave Rewards wallet options. (#17154)
  • Updated default (standard) adblocking to generally allow first-party requests. (#17366)
  • Removed known user tracking parameters from URLs. (#17507 1, #17452, #17451)
  • Fixed overlapping text in download infobar. (#17313)
  • Fixed Brave specific URLs not being listed under brave://about. (#17299)
  • Fixed inability to remove IPNS keys under brave://settings/ipfs/keys. (#17484)
  • Fixed issue with IPFS shutdown and restart in certain cases. (#16978)
  • Upgraded Chromium to 94.0.4606.61. (#18333) (Changelog for 94.0.4606.61 1)


Level 50
Content Creator
Apr 24, 2016


Level 26
Content Creator
Oct 23, 2014
Apparently Brave is testing out a new way to deliver ads.

But those that want to return to old system notifications you can do the following

“For anybody whose Brave Ads were working fine as System Notifications, and would like to continue using the System Notification route, you can go to brave://flags/, then search for (and disable) brave-ads-custom-notifications.”



Level 62
Mar 29, 2018
What’s Brave Done For My Privacy Lately? Episode #11: Debouncing

What’s Brave Done For My Privacy Lately? Episode #11: Debouncing​

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 (@fanboynz), and was written by Director of Privacy Peter Snyder.

The TL;DR;

Brave is releasing additional protections against certain forms of bounce tracking. We call these new protections “debouncing”. As of desktop version 1.32, Brave will protect users against bounce tracking by recognizing when the user is about to visit a known tracking domain, skipping visiting the tracking site all together, and instead directly navigating the user to the intended destination. Debouncing is available in nightly versions of Brave now, and will be rolled out to all Brave users shortly.

Bounce Tracking (or, Jerks Refuse to Take “No” for an Answer)

Bounce tracking is another technique trackers use to try and violate your privacy and follow you around the Web. Bounce tracking is an attempt to circumvent restrictions on third-party storage in privacy-focused browsers. The technique works by injecting additional sites between a site you’re visiting, and the site to which you intend to navigate. These intermediate sites over time learn what sites you’ve visited, and so can perform the same kinds of tracking sites used to use third-party cookies for.
As a simplified example of how bounce tracking works, consider the following example. A browser user is visiting the site site-one.example, and clicks on a link to go to cats.example. Later, the same user visits a different site, site-two.example, and clicks on a link to go to cars.example. This could look like the below.

Bounce trackers change the above, desirable situation by inserting a new, unwanted, tracking site in each navigation. When a user clicks on a link to cats.example, they’re instead taken to an unrelated site, at an URL like https://tracker.example/record?dest=cats.example. The tracking site then records that the user is interested in cats.example, and then quickly redirects the user to cats.example. The same process might then repeat when the user tries to visit cars.example; the user is instead directed to tracker.example, which learns that the same person that was interested in cats is also interested in cars, before redirecting the user to the intended page on cars.example. This might look like the below.

“Debouncing” to Defeat Bounce Tracking

Brave’s new debouncing feature protects users against bounce tracking by observing when (using the above example) the browser is about to visit tracker.example, recognizing that the “dest” parameter includes the intended destination URL, and replacing the navigation to tracker.example with the intended final URL. Brave’s “debouncing” feature not only protects users against bounce tracking among websites, but also bounce-tracking URLs used in other places on the web, including links in affiliate marketing emails.
Brave uses a Brave maintained list to identify bounce tracking URLs. This list is maintained by Brave, and is drawn from a mix of crowd-sourcing and existing open-source projects, including the terrific URL Tracking Stripper extension, Link Clearer extension, and Clear URLs extension, along with additional rules maintained by Brave. Brave will maintain this combined list going forward and welcomes collaboration with other similar projects.

One More Defense Against Bounce Tracking

Debouncing is yet another way Brave protects users against bounce tracking. Debouncing exists alongside other bounce tracking protections in Brave: query parameter stripping and warning users when they’re about to visit a suspected bounce tracking site. Brave is planning additional protections against bounce tracking as well, which we are excited to announce shortly. Brave is also working in the W3C to help standardize protections against bounce tracking and the broader category of “navigation based tracking”.
Brave’s bounce tracking protection is just another way Brave protects your privacy online. To give a few examples, Brave prevents traditional trackers by blocking third-party cookies, using a system we call site-length, ephemeral third party storage. Brave prevents trackers from using browser fingerprinting to identify (and re-identify) you by randomizing your browser fingerprint, and Brave further prevents sites from tracking you by blocking (and sometimes replacing) known tracking scripts.
Also this blog post #5: Encrypting DNS Zone Transfers | Brave Browser