Brave Brave Browser release info

oldschool

Level 59
Verified
Mar 29, 2018
4,857
A message from Brave:

Hello Brave Community,
The Brave team is always trying to find ways to improve our product and create a more enjoyable user experience for all of you. One of the most common ways we (as well as most other software developers) go about ensuring the quality and integrity of fixes/new features in the browser is by sending them through the release pipeline. This ensures that new changes to the browser have had a chance to be rigorously tested and adjusted so that issues can be addressed before they make it to the Brave stable release.

While we do a lot of testing and quality assurance all on our own, we also rely on our users to help spot new issues and report on what’s not working. However, we have recently noticed a gap in this process that we would like to address. Out of all Brave builds, it appears that we have the fewest active users on our Beta build—a key stop in the development pipeline. Brave Beta is the final stop before new code gets pushed into Brave’s stable release, which is the version available for download from brave.com, and the daily driver for most Brave browser users.

As such, we need as many eyes on Beta as possible to test and report bugs/problems in the build, allowing us to make the necessary adjustments and remove any issues before they are pushed to the majority of our user base. It is also important to note that installing Brave Beta will not overwrite any Brave installations you have on your device currently, nor will any of your associated browsing data be overwritten. All Brave browser builds are designed to run in parallel with one another (they can all run at the same time).

If you want to help Brave provide the best possible experience for its users, we invite you to try Brave beta today and share your feedback. You can download Brave Beta at

Download Brave Beta | Brave Browser
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.

You can provide feedback on the build, and report any issues or bugs on our Beta Builds section here on Community.
 

Spawn

Administrator
Verified
Staff member
Jan 8, 2011
20,681
OP: Opens fiverr.com website, gets a Brave Ad about fiverr.com

Response from Brave Rewards Team:
Brave Ads are contextual. As in the context is built for a user based on their usage and saved for users on their browser only (no server involved) and only when those users opted in to Ads to earn BAT. Ads selection also happens on the browser vs. a server - the server just sends a catalog of ads with intended targets (contexts) and advertising text, links.

The fiverr example is just serendipitous vs. intended; as in the context was built for a target fiverr intended to serve and fiverr was an advertiser. However, any advertiser with that context target could have been served - so double serendipity that fiverr was served. Actually proves the system is blind - aka serving fiverr on top of a fiverr page is not a great use of advertiser BAT.

Re: foreground vs. background; the user pushback on background Ads on Mobile was tremendous that we are now serving only when the users are active on the browser. Ads are served via the browser itself so the browser has to be running in all cases. To be clear, ads are not actively served against page context.
serendipitous = by chance or unexpected
 

oldschool

Level 59
Verified
Mar 29, 2018
4,857
@oldschool I am using brave on desktop and I have allowed all ads in global shield defaults and use brave adblock only to upgrade to https and block fingerprinting but everytime i clean cookies and stuff, it starts blacking ads and shield default is set to standard. Is there any solution to this problem?
Make sure you have Settings > Clear browsing data > Site and shields settings = UNCHECKED. Let me know if that takes care of it.
 

Upendra19

Level 5
Mar 5, 2019
207
Make sure you have Settings > Clear browsing data > Site and shields settings = UNCHECKED. Let me know if that takes care of it.
It works if I use clean from within browser but if I use bleachbit to clean my PC which doesn't have Brave cleaning options but still cleans it :unsure:, shield settings are again set to standard. I don't know what to do now.
 

oldschool

Level 59
Verified
Mar 29, 2018
4,857
Latest Brave release: Version 1.11.101 Chromium: 84.0.4147.89 (Official Build) (64-bit)

Desktop
Release Notes V1.11.101
  • [Security] Filtered sensitive information from brave://rewards-internals logs. (#10875)
  • [Security] Added disclaimer to brave://rewards-internals page. (#10873)
  • Fixed issue where browser would freeze on launch in certain cases. (#9481)
  • Fixed crash with Wayback Machine info bar in certain cases. (#10764)
Stay Brave, stay safe and enjoy! (y) :D
 

oldschool

Level 59
Verified
Mar 29, 2018
4,857
In case you make use of Brave Rewards, this info is from: The Brave Developers

Dear Brave Community,
As you may have noticed, some Community threads surrounding Ads have become “unlisted” on the forum, and you may have even seen a DM you sent one of us get deleted. We’d like to provide some context around these actions, to clear up any worries.

What was the issue?
Prior to the release of Brave stable version 1.11.101, there was an issue where the brave://rewards-internals Logs page contained too much information, some of which could lead to loss of funds if it fell into the wrong hands. This additional information was noticed thanks to user hihouhou on HackerOne and a fix was released shortly thereafter to remove the sensitive data from the logs. However, this also forced us to think about how these logs and other sensitive information often required to resolve Rewards issues ought to be collected and processed.

Up until this point, the process was to essentially assess a user’s support request on Community (or other social platforms) and, if necessary, request that the users send us a private message containing their brave://rewards-internals information, often including their internals Logs. We would then look through those direct messages, match the user to the thread, and pass the information to the appropriate teams for further investigation.
As our user base has grown, we realized that this does not scale well. It can be hard to stay organized, ensure that everyone’s information is sent securely, while maintaining a reasonable turnaround time for Rewards/Ads issues.

What are we doing to improve this process?
Since fixing the above-mentioned issue with Logs data, the team has been discussing how to best move forward with collecting user information for technical support. We’ve come up with a plan that we think will be effective, but will require some downtime. Our current plan moving forward is to:

Stop collecting brave://rewards-internals **log data (specifically) through any medium:**It is for this reason that you may have seen certain threads set to “Unlisted” or a DM you sent to a member of the Support team get deleted. In short, we needed to halt the old process so that users would not continue to send us their information, and to remove any potentially sensitive data we may have had stored anywhere. This policy will continue moving forward.
  • Note: This applies to logs data specifically. The Support team may still ask you for your brave://rewards-internals wallet ID/data (General info tab). This is because the information is safe to give (privately)
**Implement a single, official place for users to submit Logs data securely:**With all this said, we will still need to collect Logs data in order to resolve a number of Rewards issues, particularly those related to Brave Ads. As such, we are creating an official page for users to upload their Logs data safely and securely. The goal is to eventually have any/all Rewards data submitted there (wallet info, logs or otherwise), and to eliminate the need for Support to sift through individual DMs/threads. We are working hard to get this implemented as soon as possible and will inform everyone once it’s ready.

  • Note: While we work on implementing an official path for users to upload their data, we are putting a temporary “hold” on resolving support issues that require logs data. We understand that this is not ideal and that many users will have to wait to get their issues resolved, but we believe that this temporary wait is preferable to requesting/receiving data in a manner that is anything less than 100% secure. We truly appreciate your patience and understanding. We anticipate development time to only be a couple weeks or less.
 
Top