Welcome @beduffymp , @bebravealways , and @haiku . Others have reported similar problems and investigation yielded they were using the old Muon-based version of Brave, not evidence of bias in the blacklists. If you go to About Brave or another way to check version and have something like 0.25.xx (maybe 0.26.xx), that’s Muon and no longer supported. @Mattches has several posts in similar threads explaining.
Some months ago, Brave switched from Muon to Chromium underpinnings. The fix is to download and install the new version from https://brave.com/download and import your data (probably best to back up your User Data folder and Wallet , first, just in case). See this Help page about updating from Muon to Core (the new one).
Also, this has useful information:
@nellaiseemai , excellent question! I will address this directly, but I’m going to broaden the scope of your question a bit as I think others would benefit from knowing these things.
This is both a very exciting time for Brave users (and staff!). The transition to the new build/1.0, a Beta release, Developer release, and live “stable” build (Muon) may be confusing to users who may not have been exposed to the concepts of an open source project or the software development process. So I’ll take a …
And for examples of similar reports, see:
Evereyone:
The reason you’re all seeing this is likely due to the fact that the list Muon uses for Malware Detection is blocking scripts on those pages that may or may not actually contain malware. It’s hard to say, given that we haven’t updated those lists in a while – months at least.
This is because, and I cannot stress this enough – we are no longer supporting Muon officially. Brave Core (that is, the version that leverages the chromium UI) is the officially supported release and has the m…
andhttps://community.brave.com/t/unblock-the-news-observer/49911 https://community.brave.com/t/unblock-twitch/50491
1 Like