Updates Brave Browser release info

silversurfer

Level 74
Verified
Trusted
Content Creator
Malware Hunter
Aug 17, 2014
6,331

Brave Release Channel 1.25.72​

Full Release Notes​

  • Fixed Brave Shields not respecting per website settings. (#16265)
  • Fixed $csp rules still being applied when Brave Shields has been disabled. (#16283)
  • Upgraded Chromium to 91.0.4472.101. (#16314 1)
 

silversurfer

Level 74
Verified
Trusted
Content Creator
Malware Hunter
Aug 17, 2014
6,331

Brave Release Channel 1.25.73​

Full Release Notes:
  • Fixed Brave Shields appearing disabled even though enabled in certain cases. (#16362)
  • Upgraded Chromium to 91.0.4472.106. (#16314)
 

silversurfer

Level 74
Verified
Trusted
Content Creator
Malware Hunter
Aug 17, 2014
6,331

Brave Release Channel 1.26.67​

Full Release Notes:
  • Added Brave Search beta to the list of available search engines. (#15663)
  • Added FTX widget to the New Tab Page. (#15790)
  • Added QR code generator to the URL bar. (#15900)
  • Added explict opt-in to Brave News. (#15926)
  • Added the ability for users to import P2P keys for use with IPFS. (#15566)
  • Added the ability for users to publish content using P2P keys with IPFS. (#15422)
  • [Security] Fixed CNAME uncloaking when proxy is set as reported on HackerOne by neeythann. (#16011)
  • Updated adblocking to prevent DNS lookups for CNAME decloaking when requests are already blocked. (#15302)
  • Updated the “Learn more” link on the IPFS interstitial page and under brave://settings/ipfs. (#15829)
  • Updated the Cloudflare privacy policy link on the Unstoppable Domains interstitial page. (#15831)
  • Updated brave://version to show full variation names. (#14780)
  • Renamed Brave Today to Brave News. (#15925)
  • Removed “Block element via selector” from the Brave extension. (#15419)
  • Fixed URL bar search not working in private windows when the search provider was set by an extension. (#10601)
  • Fixed issue where users were unable to share a local file or folder using IPFS. (#16020)
  • Fixed IPFS sub menu not appearing on the hamburger menu until browser restart. (#15822)
  • Fixed Brave being registered as an FTP handler on Linux. (#15812)
  • Fixed issue where the Brave News customize button could incorrectly link to “Customize Dashboard” modal in certain cases. (#15221)
  • Upgraded Chromium to 91.0.4472.114. (#16489)
 

silversurfer

Level 74
Verified
Trusted
Content Creator
Malware Hunter
Aug 17, 2014
6,331

Brave Release Channel 1.26.74​

Full Release Notes
  • Renamed “Brave Search beta” to “Brave” in several locations including onboarding and the URL bar. (#16564 3)
  • Upgraded Chromium to 91.0.4472.124. (#16600 2)
 

silversurfer

Level 74
Verified
Trusted
Content Creator
Malware Hunter
Aug 17, 2014
6,331

Release Channel 1.26.77​

Full Release Notes:
  • Upgraded Chromium to 91.0.4472.164. (#16977 2)
 

silversurfer

Level 74
Verified
Trusted
Content Creator
Malware Hunter
Aug 17, 2014
6,331

Release Channel 1.27.108​

Full Release Notes:
  • Added new hourly options under “Maximum number of ads displayed” for Brave Ads notifications. (#16228 1)
  • Added “Don’t ask me again” button to Wayback Machine infobar. (#8497)
  • [Security] Migrated Tor log from disk to memory as reported on HackerOne by sickcodes. (#16747)
  • Implemented additional WebGL extensions blocking logic. (#15882)
  • Improved “Disconnected” Brave Rewards wallet state. (#15237)
  • Updated default search engine for new installations in certain regions. (#16870 1)
  • Updated Brave Rewards wallet verification modal under brave://rewards/#verify. (#16178)
  • Updated Brave Ads UI to show estimated pending rewards for current month only. (#15005)
  • Updated fingerprinting protections to always return light mode when set to strict. (#15265 1)
  • Fixed issue where “Current earnings this month (estimated)” incorrectly decreased in certain cases. (#16861)
  • Fixed various IPFS issues. (#17112)
  • Fixed TLS pins not working. (#15667)
  • Upgraded Chromium to 92.0.4515.107. (#17036 2)
 

oldschool

Level 61
Verified
Mar 29, 2018
5,030
Oddly enough I found this looking for current Edge/Chromium flag recommendations. For all of you Brave users out there, here it is:
 

Gandalf_The_Grey

Level 50
Verified
Trusted
Content Creator
Apr 24, 2016
3,904
Release Channel 1.27.109
Full Release Notes:
  • Fixed “Maximum number of ads displayed” incorrectly being set to 0 after upgrade in certain cases. (#17155 4)
  • Upgraded Chromium to 92.0.4515.115. (#17162 3)
 

silversurfer

Level 74
Verified
Trusted
Content Creator
Malware Hunter
Aug 17, 2014
6,331
Brave Release Channel 1.27.111
Release Notes V1.27.111 (Aug 5, 2021)
  • Fixed users not being rewarded for New Tab Page Sponsored Image views in certain cases. (#17352)
  • Fixed ads from split groups not being displayed in certain cases. (#17199)
  • Fixed Brave ads database failing to upgrade in certain cases. (#17231)
  • Upgraded Chromium to 92.0.4515.131. (#17306) (Changlog for 92.0.4515.131)
 

silversurfer

Level 74
Verified
Trusted
Content Creator
Malware Hunter
Aug 17, 2014
6,331

Release Notes V1.28.105 (Aug 11, 2021)​

  • Added display ads to the Brave News feed. (#16698)
  • Added setting to “Automatically send daily usage ping to Brave” under brave://settings/privacy. (#16583)
  • Added support for additional currencies in the Gemini widget. (#16081)
  • Added the ability for users to rotate IPFS keys. (#15568)
  • Added p2p key export for IPFS. (#16613)
  • Updated the placement of “Privacy and security” section under brave://settings. (#16470)
  • Updated the custom header list to be hard-coded. (#16455)
  • Updated adblocking to collapse HTML elements with blocked image or iframe requests. (#14960)
  • Updated icons used for certain file types when Brave is set as the default application. (#12761)
  • Updated the bookmarks folder icon on the bookmarks bar. (#16940)
  • Updated the Ads History view from 7 days to 30 days. (#16627)
  • Removed duplicate separator under right click context menu. (#15714)
  • Fixed Brave Rewards wallet being reset after upgrading in certain cases. (#16449)
  • Fixed IPFS migration. (#16913)
  • Fixed “Connected peers” not being reset to 0 once IPFS node is stopped. (#16804)
  • Fixed delete button not appearing on brave://history when using the search box. (#7398)
 

silversurfer

Level 74
Verified
Trusted
Content Creator
Malware Hunter
Aug 17, 2014
6,331

oldschool

Level 61
Verified
Mar 29, 2018
5,030
Chef Koch is keeping his hardening guide updated. (y) (y)
 

silversurfer

Level 74
Verified
Trusted
Content Creator
Malware Hunter
Aug 17, 2014
6,331
Release Notes V1.29.76 (Aug 31, 2021)
  • Added Gemini two-way Brave Rewards wallet. (#17161)
  • Added prompt to enable crash reporting. (#1841)
  • Added support for launching Brave with a Tor window when using the terminal/command line interface. (#2105)
  • Added “Show Search Tabs button” setting under brave://settings/appearance. (#16007)
  • Added “walletActive” parameter to the stats usage ping. (#17059)
  • Added ephemeral support to “BroadcastChannel”. (#17220)
  • Added Uphold user ID under brave://rewards-internals to assist with rewards support. (#16937)
  • Added a “Relaunch” button which displays after the in-line “Tips Settings” are modified. (#16941)
  • Changed the location of QR code for iOS devices to be under the “Manage Your Wallet” modal on brave://rewards page. (#16954)
  • Updated the date of installation parameter in the stats ping to expire in 30 days. (#17089)
  • Reduced the height of the download bar. (#1638)
  • Removed the Brave Rewards semi-verified user wallet state which occurred in certain cases. (#15390)
  • Fixed IPFS links not being fully displayed in the Brave Rewards panel. (#16612)
  • Fixed mute button moving when hovering on an inactive tab. (#16860)
  • Fixed the close “x” button not being shown on tab hover with small tab size on macOS. (#13946)
  • Fixed inconsistent capitalization in menu items on Windows and Linux. (#17309)
  • Upgraded Chromium to 93.0.4577.58. (#17668) (Changelog for 93.0.4577.58)
 

silversurfer

Level 74
Verified
Trusted
Content Creator
Malware Hunter
Aug 17, 2014
6,331

Release Channel 1.29.77​

Full Release Notes
 

silversurfer

Level 74
Verified
Trusted
Content Creator
Malware Hunter
Aug 17, 2014
6,331
Release Channel 1.29.79

Full Release Notes:
  • Fixed issue where site settings were not being retained in certain cases. (#17859 2)
  • Fixed invalid certificate error being displayed when visiting “*.eth.link” sites. (#17815 1)
  • Fixed issue where images were not being displayed for the promo cards under brave://rewards page in certain cases. (#9553 2)
 

oldschool

Level 61
Verified
Mar 29, 2018
5,030
Check Chef Koch about:flags Brave for more suggestions.
In case you missed it, there are helpful sections at bottom of page on useful & non-useful extensions, etc. The best things about his hardening guide are the many references included with his suggestions and tips so users can check for themselves as to usefulness, trustworthiness, etc.
Here's one example:
ClearURLsUntil merged with Brave adblock (needs syntax changes in Braves AdBlock).
Going to Brave adblock you see more info on custom rules re: url tracking link cleaning.

I'd say his guide is the closest thing to arkenfox.js for brave and worth reading for information purposes alone, regardless of implementation. (y)
 
Last edited:

silversurfer

Level 74
Verified
Trusted
Content Creator
Malware Hunter
Aug 17, 2014
6,331

Release Channel 1.29.80​

Full Release Notes:
  • Updated the bookmarks folder icon on the bookmarks bar. (#17463 2)
  • Fixed Chromecast crashing in certain cases and re-added “Media Router” setting (disabled by default) under “brave://settings/extensions”. (#17873)
  • Fixed crash when opening brave://settings/content/autoplay. (#17808 1)
  • Fixed Brave Talk not being recognized when rewards is enabled due to Greaselion precondition not being met with multiple profiles. (#17914 3)
 

silversurfer

Level 74
Verified
Trusted
Content Creator
Malware Hunter
Aug 17, 2014
6,331
Brave Release Channel 1.29.81

Full Release Notes:
 

oldschool

Level 61
Verified
Mar 29, 2018
5,030

What’s Brave Done For My Privacy Lately? Episode #9: Improving Privacy By Improving Web Compatibility​

This is the ninth in a series of blog posts on new Brave privacy features. Author: Peter Snyder, Director of Privacy and Senior Privacy Researcher. Implementation: Anton Lazarev, Research Engineer.

In order to improve privacy and Web compatibility, Brave will by default not apply network level filter list blocking to same-site1 subresources, starting in version 1.30, or the Beta and Nightly versions at time of this posting2. Brave will continue blocking third-party requests as it currently does, using the crowdsourced information gathered by EasyList, EasyPrivacy, uBlock Origin and similar projects. This change is being made for two reasons. First, recent privacy protections in Brave protect users from the kinds of tracking first-party subresources can carry out (e.g. fingerprinting). Second, this change aims to reduce how often Brave users have to “drop shields” (i.e. disable Brave’s privacy protections) to use certain sites, leaving those Brave users exposed to the worst kinds of privacy harm.

This change affects only the default settings; Brave users who wish to retain current, more aggressive but occasionally-website-breaking behavior can do so by setting the “trackers and ads blocked” setting in Shields to the “aggressive” setting. Brave’s goal is to create the best-in-class privacy protecting browser, to provide defaults we think best suit most users, and to leave the user in full control if they want to block more content. Finally, Brave will still selectively block first-party subrequests when we know they are user-harmful or unwanted. The policy change described in this post describes only a change in the default policy.

As with all changes, we’d appreciate your feedback. The best place to provide feedback is at Brave Community. Any notes or observations you have about whether this change seems to decrease (or increase) how often you need to drop shields when using Brave would be particularly appreciated.

Changing Shields Behavior Will Improve Privacy
Brave is disabling filter list blocking for first-party subresources to improve privacy for typical Brave users. Advanced users still have the ability to deploy more aggressive privacy protections, even those that might break sites. This change disables blocking in cases where privacy risk is the smallest, in order to improve Web compatibility and reduce the frequency of the worst case privacy outcomes. By default, Brave blocks network requests for tracking and Web annoyance resources, as determined by popular, crowd sourced filter lists. Filter list based blocking has many benefits; blocking improves performance, saves battery life, and (in the absence of other protections) improves privacy. However, Brave features such as blocking third party cookies, ephemeral third-party storage and browser fingerprint randomization provide platform wide defenses against the kinds of privacy harms other browsers need filter lists to protect against.

Because of these other privacy features in Brave, some added more recently, the largest privacy gain from filter-list blocking is in preventing third-parties from learning your IP address; there is much less privacy benefit in blocking first party requests, because the first party already knows your IP address. While there can be some privacy benefit in blocking some first-party subrequests, such cases are ad hoc and depend on developer implementation decisions, instead of fundamental aspects of the Web. Filter list based blocking comes with significant downsides too. For example, filter lists can fall out of date causing performance and compatibility problems. More significantly, filter list blocking can break sites requiring users to disable Brave’s privacy protections (i.e. “dropping shields”) to use a site. Dropping shields is the last resort for trading user privacy against site compatibility, as it disables all of Brave’s privacy protections on the site, to maximize the chance of un-breaking the page. Users who drop shields may wish they re-raised them at a later date, but often won’t remember to do so.

And while advanced users can use Brave Shield’s more advanced settings to apply narrower, more surgical interventions to unbreak sites, doing so is beyond what most users can do and should have to do, to use the Web.

Differences Between Standard and Aggressive Blocking
Brave offers users three levels of tracking protection, configurable through Brave Shields:
  • Trackers & and ads blocked (aggressive): Apply all Brave blocking and filtering tools, even those with an increased risk of breaking sites.
  • Trackers & and ads blocked (standard): This is the default policy in Brave. Apply the blocking and filtering approaches Brave thinks provides the best privacy for most Brave users.
  • Allow all trackers & ads: Apply no blocking or filtering tools.
The below table details the differences between the aggressive and standard blocking levels.

Standard (default)Aggressive
Cosmetic filteringHide page elements related to third-party advertisingHide page elements related to first and/or third party advertising
Network filteringApply filter lists to all third-party sub-resource requestsApply filter lists to all sub-resource requests, first and third-party alike
Bounce trackingStrip known tracking query parameters from URLsStrip known tracking query parameters from URLs and warn users before navigating to suspected bounce tracking domains

How to Maintain the Current Shields Behavior
Advanced Brave users who wish to maintain the existing blocking behavior can do so in two ways.

The first option is to change Brave’s blocking settings to Trackers & and ads blocked (aggressive). This can be done for all, or specific, sites by configuring Shields. The second option is by visiting brave://flags and disabling the #brave-adblock-default-1p-blocking setting.

1 Same-site, or first party, subresources here refers to requests for images, scripts, or other page elements that come from the same site as the page requesting those subresources. If you are on Welcome to cats.com Created in 1991 15,000+ visitors per month, https://cats.com/logo.png and https://food.cats.com/kibble.js are both examples of same-site subresource requests, while https://dogs.com/logo.png would be a third-party sub resource request.
2 These changes are being rolled out to users over the next 24 hours, and should be live on Nightly and Beta releases by end-of-day on Sept 2, 2021.
What’s Brave Done For My Privacy Lately? Episode #9: Improving Privacy By Improving Web Compatibility
 
Top