- Jan 27, 2018
- 1,266
Whhattttt, Frank Zappa, I thought that was old school's mug. Dam.
Brave Browser release info
- Thread starter oldschool
- Start date
Whhattttt, Frank Zappa, I thought that was old school's mug. Dam.
- Mar 29, 2018
- 7,136
I thought Brave users might appreciate this info:
New development schedule delivers features and fixes for general release in 3-6 weeks instead of 6-9 weeks
When features and fixes get implemented for Brave, they make their way through 4 distinct browser channels. This happens on a schedule 2 which is determined more than a year in advance.
These browser channels are described as follows:
For changes that we don’t uplift though, it takes 6-9 weeks to get the change to the Release channel where most of the user base exists.
After today, we’ll be reducing the time it takes for a change to make it to the Release channel from 6-9 weeks to 3-6 weeks. This will be accomplished by making our Dev channel go directly from 1.5.x to 1.7.x, skipping over the 1.6.x version. Dev channel will be equivalent to Beta channel.
For most users, starting today there will be three channels to choose from: Nightly, Beta, and Release.
We’ll still continue to build both Dev and Beta channels, but they’ll be served from the same code. Dev channel will get updates nearly every day, Beta channel will get updates a couple times a week. We’ll update brave.com 3 to deemphasize Dev channel more, but the download page will remain available. The Nightly channel will not be affected in any way.
Besides noticing the skipping of the 1.6.x version, we don’t expect this will impact any Brave user of any channel in any way. This is being done so we can ship things faster without needing to uplift the changes.
New development schedule delivers features and fixes for general release in 3-6 weeks instead of 6-9 weeks
When features and fixes get implemented for Brave, they make their way through 4 distinct browser channels. This happens on a schedule 2 which is determined more than a year in advance.
These browser channels are described as follows:
- Nightly 1: For users who want to stay on the cutting edge, and are willing to live with the bugs that come with it. This channel makes up the smallest user base. When features and fixes first get implemented, they land here first.
- Dev: 0-3 weeks after changes land on Nightly, they move to this channel.
- Beta: For users who’d like to experience new features in advance of release, and are willing to tolerate some bugs. 3 weeks after changes have been on Dev, they move to this channel.
- Release 1: This channel makes up our largest user base. 3 weeks after changes have been on Beta, they move to this channel. This channel is for the vast majority of users, this is the most tested, most stable version of Brave.
For changes that we don’t uplift though, it takes 6-9 weeks to get the change to the Release channel where most of the user base exists.
After today, we’ll be reducing the time it takes for a change to make it to the Release channel from 6-9 weeks to 3-6 weeks. This will be accomplished by making our Dev channel go directly from 1.5.x to 1.7.x, skipping over the 1.6.x version. Dev channel will be equivalent to Beta channel.
For most users, starting today there will be three channels to choose from: Nightly, Beta, and Release.
We’ll still continue to build both Dev and Beta channels, but they’ll be served from the same code. Dev channel will get updates nearly every day, Beta channel will get updates a couple times a week. We’ll update brave.com 3 to deemphasize Dev channel more, but the download page will remain available. The Nightly channel will not be affected in any way.
Besides noticing the skipping of the 1.6.x version, we don’t expect this will impact any Brave user of any channel in any way. This is being done so we can ship things faster without needing to uplift the changes.
- Mar 29, 2018
- 7,136
Brave update
Version 1.5.112 Chromium: 80.0.3987.132 (Official Build) (64-bit)
Desktop
Release Notes V1.5.112
Version 1.5.112 Chromium: 80.0.3987.132 (Official Build) (64-bit)
Desktop
Release Notes V1.5.112
- Added ad conversion attribution for Brave ads. (#6536)
- Added ability for websites to determine if browser is Brave. (#8216)
- Improved compatibility with MetaMask and allow web3 provider selection. (#7503)
- Improved fingerprinting privacy by removing “navigator.deviceMemory”. (#1157)
- Removed reference to star icon used to bookmark pages under the bookmark manager. (#2494)
- Updated top sites background from translucent to opaque under New Tab Page. (#6642)
- Updated text in the “Ads” panel under brave://rewards. (#7500)
- Fixed favorites and bookmarks not importing from Safari. (#2710)
- Fixed intermittent crash if ad confirmations library is called before being instantiated. (#7728)
- Fixed 5% fee for Brave Rewards not always being sent when multiple tips are sent in quick succession. (#7425)
- Fixed all confirmation types such as viewed, clicked and dismissed being counted towards the ads per hour limit. (#8539)
- Fixed incorrect message being displayed on panel and tip banner in certain cases. (#7739)
- Fixed duplicate ads entries not being added into “7-day Ads History” in brave://rewards. (#7869)
- Fixed incorrect color being used for the “thumbs up” icon in “7-day Ads History” under brave://rewards. (#7437)
- Fixed PDFium displaying “Brave Software Drive” in the “Save as PDF” modal. (#5450)
- Fixed shields content should be specific to the page that the shields panel is opened from. (#6601)
- Fixed shields warning not visible when changing between advanced vs simple view while using dark theme. (#7628)
- Fixed “brave-browser.list” being removed on Linux whenever upgrading Brave. (#6912)
- Mar 29, 2018
- 7,136
Here's some informative post from the Brave Community:
Specifically re: Google Tag Manager
Brave ships with strong default privacy protection from multiple levels, but the user has agency over their global and site-level protection settings. We make these settings accessible from the URL bar, and include a link directly to global settings.
Our users expect a stronger level of default privacy protection and security from our product, and our mission is to execute and deliver new business lines that can operate and scale with the platform.
The first-order is to provide default privacy in a way that can scale for mainstream users without wrecking the experience.
In parallel, we’ve introduced new alternative protocols, and deployed them across millions of browsers in the wild. This is the groundwork that can help drive broader privacy protocol adoption, but the fundamentals must function for users first. Otherwise, we’d likely be on a short path to being the neatest science experiment for privacy collecting dust on a shelf.
As we scale, the growth becomes of higher interest to publishers, and becomes a forcing-function to continue to adapt existing platforms to accept new protocols. We’re already doing this from the advertising side. We have +400K creators and publishers that have verified to accept revenue from our platform (https://batgrowth.com 1). Interest and experimentation from publishers has been growing with our user base.
There are a handful of different privacy approaches being introduced in-market. iTP has an impact in a major way. Google is trying a lighter approach. We have been consistently leading and executing on one of the strongest privacy approaches, and are aiming to prove out the revenue model for publishers at scale, as we scale.
Hope this wasn’t too vague, but the privacy model is a bit different. Hope it helps with context.
Specifically re: Google Tag Manager
- Privacy and security risks in permitting 3rd party network requests to Google through the Google Tag Manager service, within the Google Marketing Platform.
- The request to Google’s marketing servers is made without the user being aware of the invocation.
- For added context, these are the measures we take to protect the user from leaking network requests to Google from the core browser code: brave/brave-browser
- https://blog.sucuri.net/2018/04/malicious-activities-google-tag-manager.html
- https://blog.littledata.io/2018/11/24/stop-gtm-being-hacking/ 1
Brave ships with strong default privacy protection from multiple levels, but the user has agency over their global and site-level protection settings. We make these settings accessible from the URL bar, and include a link directly to global settings.
Our users expect a stronger level of default privacy protection and security from our product, and our mission is to execute and deliver new business lines that can operate and scale with the platform.
The first-order is to provide default privacy in a way that can scale for mainstream users without wrecking the experience.
In parallel, we’ve introduced new alternative protocols, and deployed them across millions of browsers in the wild. This is the groundwork that can help drive broader privacy protocol adoption, but the fundamentals must function for users first. Otherwise, we’d likely be on a short path to being the neatest science experiment for privacy collecting dust on a shelf.
As we scale, the growth becomes of higher interest to publishers, and becomes a forcing-function to continue to adapt existing platforms to accept new protocols. We’re already doing this from the advertising side. We have +400K creators and publishers that have verified to accept revenue from our platform (https://batgrowth.com 1). Interest and experimentation from publishers has been growing with our user base.
There are a handful of different privacy approaches being introduced in-market. iTP has an impact in a major way. Google is trying a lighter approach. We have been consistently leading and executing on one of the strongest privacy approaches, and are aiming to prove out the revenue model for publishers at scale, as we scale.
Hope this wasn’t too vague, but the privacy model is a bit different. Hope it helps with context.
- May 3, 2015
- 1,540
All right you convinced me.... testing Brave now.
- Mar 29, 2018
- 7,136
Nothing like frequent updates! 
Version 1.5.113 Chromium: 80.0.3987.149 (Official Build) (64-bit)
Desktop
Release Notes V1.5.113
Version 1.5.113 Chromium: 80.0.3987.149 (Official Build) (64-bit)
Desktop
Release Notes V1.5.113
- Upgraded Chromium to 80.0.3987.149. (#8728)
- May 10, 2019
- 1,854
I've just received the updated on Elementary OSNothing like frequent updates!
Version 1.5.113 Chromium: 80.0.3987.149 (Official Build) (64-bit)
Desktop
Release Notes V1.5.113
- Upgraded Chromium to 80.0.3987.149. (#8728)
- Mar 29, 2018
- 7,136
There is an update to Brave Version 1.5.114 Chromium: 80.0.3987.149 (Official Build) (64-bit) via a standalone installer. I believe this fixes high CPU issues some users were experiencing. There are no current release notes available. Maybe this will get pushed next week?
Or you may get it here v. 1.5.114 Enjoy!
Or you may get it here v. 1.5.114 Enjoy!
- Aug 4, 2016
- 1,465
Thanks for link installed - Getting used to Brave & likely to keep using it despite the occasional spasm to go to me New Edge installer but I resist
- Mar 29, 2018
- 7,136
Version 1.5.115 Chromium: 80.0.3987.149 (Official Build) (64-bit)
Release Notes
Release Notes
- Fixed CPU/performance issues in certain cases. (#8779)
- Mar 16, 2019
- 3,645
Do they have any plans to add the feature to open new tab with middle mouse button?
- Mar 29, 2018
- 7,136
I don't know.
I just installed the v1.5.115. I'll be using it for sign-in accounts ONLY like forums, emails, banking, shopping and social media. FF will be used for everyday general surfing WITHOUT signing in. That is practicing browser compartmentalization.
Questions
1) What are the flag settings to harden Brave?
So far using the following extensions
1) I don't care about cookies
2) Forget Me Now
Questions
1) What are the flag settings to harden Brave?
So far using the following extensions
1) I don't care about cookies
2) Forget Me Now
Last edited:
- May 10, 2019
- 1,854
Heimdal Thor Premium home blocks Brave bowser download! Really?
- May 10, 2019
- 1,854
- Mar 29, 2018
- 7,136
- May 10, 2019
- 1,854
Downloaded the installer from Softpedia
- Mar 29, 2018
- 7,136
@HarborFront you shouldn't need this flag: Enable cosmetic filtering. I had it enabled by mistake.
- Aug 17, 2014
- 10,210
Just trying out to download from homepage:
Secure, Fast, & Private Web Browser with Adblocker | Brave
The Brave browser is a fast, private and secure web browser for PC, Mac and mobile. Download now to enjoy a faster ad-free browsing experience that saves data and battery life by blocking tracking software.
brave.com
- May 10, 2019
- 1,854
Tried downloading from the main website using Vivaldi and Microsoft Edge. Heimdal Thor Premium Home blocks the download. Contacted support to make sure it is a false positive.Just trying out to download from homepage:
Secure, Fast, & Private Web Browser with Adblocker | Brave
The Brave browser is a fast, private and secure web browser for PC, Mac and mobile. Download now to enjoy a faster ad-free browsing experience that saves data and battery life by blocking tracking software.
