Shivan
Shivan
We think this should have gotten fixed by https://github.com/brave/adblock-lists/pull/2509, can you check @fmarier?
These seem like two different lists
If the exception was never working in the first place, then do we even need this rule?
@boocmp @iefremov We do have issues with Speedreader + network blocking too: https://bravesoftware.slack.com/archives/CLX7EV42Z/p1726603890011589?thread_ts=1726595972.638809&cid=CLX7EV42Z
Spoke with @boocmp and I understand now that network blocking is not relevant here, at least for the [issue I mentioned](https://bravesoftware.slack.com/archives/CLX7EV42Z/p1726603890011589?thread_ts=1726595972.638809&cid=CLX7EV42Z). Let's go with just CF disabling.
(also just FYI @antonok-edm)
@boocmp how do we handle naming collisions? For instance, if a user tries to create a new scriptlet called `brave-fix` which conflicts with an existing scriptlet, how do we handle...
We're actually looking into separating `block elements` custom filters into a separatable thing anyway.
The following would be useful: 1. Have a sentence above "N fingerprinting protections applied" saying "These APIs were used on this page which Brave farbled. Learn more here." 2. Learn...
cc @rmcfadden3 would appreciate help with the wording