Just wanted to inform everyone that we do have an open issue for the Shields view (advanced vs simple) not persisting here:
The whole point is that NOBODY here has made a feature request which makes the Brave Shields less easier to use.
Brave developers have much more important things to focus on in regards to improving security and privacy, it is irrational for them to waste hours of valuable time making changes to the Brave Shields interface which make them less easy to use and introduce changes NOBODY requested.
I do appreciate being able to use v1 Shields. I hope these features aren’t further regressed in the future
I think they removed the flags all together (v1, v2) in the latest update Brave 1.42, chromium 104.
I defaulted to version 2 directly after the update.
Pretty bad. I liked the UI of v1. It was simple, compact, good looking.
Other related background information.
Source: User Solutions: Brave Release 1.42.x
Selected Topics: Brave GitHub → In the Works: Selected GitHub Issues/Projects → ANNOYANCE ISSUES:
ShieldsBlocked Scripts “Allow Specific Scripts” Option
The feature and workaround as provided in previous versions has been removed. Related post from Brave staff with background information:
Brave GitHub Issue Report(s):
Feature to allow individual scripts is gone in Brave Shield v2 #22601
Shields Panel #22625
‘It allows the scripts to load, or it gets outed as a customer of epstien island.’
Billionaires gonna protect their billions.
The removal of the flags which enabled us to use v1 Shields is one step too far by the developers of Brave.
They are simply NOT listening to what Brave users want.
It is time to dump Brave and look for a new browser.
Yeah, somehow I doubt that the tech giants are gonna let us be free enough that their privilege is threatened.
They have to know everything at every moment or they might get toppled.
That means fedbook and boogle scripts must load.
The brave devs know exactly what they have done.
I’m sure they are just following orders from the billionaire that signs their slave wage checks.
(How can I be a slave, I get a paycheck?)
If you find one, post it here so we can all move to a project that values us as crowd sourced wisdom.
Ya please post if anyone finds a suitable replacement. I’d be willing to give it a try.
ungoogled chromium isn’t bad but its a pain to add extensions.
Librewolf, comes preinstalled with Ublock-origin. A pretty solid browser from privacy point of view.
From privacy standpoint on chromium side only brave is good.
The closed issue reports have a couple of posts with suggestions on alternatives. Linking a post with additional information that I posted in another topic and copy/pasting quotes below.
Also, just to give some context to why the per-script controls were removed from Brave in the first place, we decided to remove the feature for three reasons:
- Brave shipped a number of other on-by-default privacy features that reduced the privacy-benefit of the per-script-controls. For example, Brave ships ephemeral, partitioned storage and randomized fingerprint protections by default (among many other features) dramatically reducing how much privacy harm most scripts can cause. Thats not to say that per-script controls aren’t still useful, just that they’re useful in less cases than they were previously.
- Chromium internals changed in a way that made maintaining the feature more difficult and costly (at least given the way were were implementing it previously)
- We evaluated uMatrix and NoScript and decided they were likely sufficient alternatives for the small number of Brave users who used the per-script controls
However, that being said, we will revisit the feature if we can find an easier way to re-implement given Chromium internals, or if we believe a significant portion of Brave users would use the feature if made available again
diracdeltas commented 08/09/22
umatrix and noscript are reasonable alternatives
if you don’t feel like installing an extension and know what scripts you want to disable or selectively enable, you can write a custom adblock filter in brave://settings/shields/filters. we can help you with the syntax for that if you want to go this route, but umatrix/noscript are much more usable for most people
That explains the so called rationale for removing the per-script controls.
Many people here have been waiting and waiting for more granular Shield controls, because with more technical development and improvements Brave Shields could be more powerful than any browser extension as the Shields are directly integrated into the browser itself.
Brave developers are going directly against what many Brave users have requested and ignoring what we want.
It is painfully obvious Brave is NEVER, EVER going to give us that control and Brave is NOT going live up to its full potential.
The new v2 Shields have a UI which consumes more space and you have to make an extra click to open the Advanced Controls and you are then confronted with the fact the v2 Shields have less functionality.
This is simply NOT GOOD ENOUGH.
It is time to dump Brave and start looking for a new browser.
I’ve been using ungoogled chromium the last couple of days. Once I figured out how to add extensions it’s working nicely with Ublock and Noscript.
Having the choice of what scripts to let loose on my browser makes a big difference as now I see I don’t have to allow everything to view a web page.
Configuring the browser is not much different than Brave and there seems to be constant work being done to the browser to improve it even more.
I tried the Librewolf but I didn’t like the layout of it in regards to the tab, tool bar looks, it looks oversized and there was no way to slim it down from what I could see. Other than that it also does what I want.
Judging by this community forum, Brave is having a lot of trouble in the ad payment section, and I wonder if thats why the shields have been crippled. If the ads are blocked then no one will read them and that messes up Braves crypto economy in some way.
Have the ad companies put pressure on Brave to cripple the shields… Just asking
Brave reward ads (BAT ads) having nothing to do with shields. Both are completely different things.
Brave ads are served by notifications and sponsored images on new tab page not on websites like wikipedia. So the questions of brave shields interfering with brave ads is out of question.
Also Ublock origin and possibly noscpripts will be useless by June 2023 when Manifest V3 kicks in on other chromium browsers like Vivaldi, Opera, Ungoogled Chromium.
Also ungoogled chromium on windows does not update mechanism both manual or automatic.
Why? And why the differentiation between uBlock(useless) and NoScripts (possibly useless)? The KISS principle works for me if you do provide some input.
Another question, would Manifest v3 make the custom filters “useless” too? Especially in relation to users (like me) who don’t use extensions.
I am trying to determine if I want to learn how to add custom filters to
brave://settings/shields/filters. I was thinking I could install uBlock to create the filter, paste it into
Create Custom filters, then uninstall uBlock. I really don’t know if this will work or not. I don’t like extensions and do not use them. This would be an exception just to get a useable script (hopefully). Link to my topic about this: Custom Adblock Filters: How To/Instructions?
Any input appreciated! Thanks.
I didn’t know about that, ty. The app makers will probably adapt though.
Also not sure if it makes a difference, But I use Linux Mint with Wireguard Vpn, not winblows.
I just wonder why if noscript and other script blockers can work, why can’t Brave make the shields work as before.
There is no need to make a filter list by yourself word by word. They are already done in hundreds by ‘experts’
Earlier when there was brave://adblock, we were just able to install this fliter lists easily. Update them easily (automatically). Now brave://adblock has been integrated into brave://shields so I will need to look into it again.
Not possible, see my links
Ty chh, I’ll check them out, I am not up to speed on this kind of stuff at all.