New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
uBlock Protector Extension - Error #2804
Comments
The reason this site thinks you use the
in |
Their detection is broken, if you actually use my extension, you won't get that as I replaced their bootstrapper with a noop function which effectively disables NoAdBlock. |
Thanks a lot for your explainations guys. OFF TOPIC: |
Unfortunately, uBlock Protector is Chrome/Chromium only, it is in the store here. Blowing up |
|
Yeah, I've blocked those elements myself. In comparison, since you're building an extension that is compatible with Google Chrome yourself, I assume that you're familiar with how incredibly invasive a browser can be! The main reason why Pale Moon has a future, as opposed to other Mozilla-based browsers, is this: |
Chrome obeys instructions from my extension as expected, I never had any problem, Firefox, on the other hand, gets in my way with its broken CSP handling (which apparently shut down the Firefox fork of uBlock Protector), I don't know how Pale Moon acts about this, but since it is a Firefox fork, it might act similarly. Firefox is way more invasive when it comes to extension development. I want to have good search result, to save my time, so I don't mind a browser that tracks me as it works better that way. You can use Chromium if you dislike tracking. Blink, the rendering engine of Chrome is also open source (although it's kind of hard to checkout the source...), I don't see why Pale Moon's rendering engine would be better as Blink is maintained by top engineers of the world. |
They may randomize it from day to day, that's how |
Judging from PM's changelogs, a lot of work has been done in that department, distancing it from Firefox. --
I simply blocked these elements, and I haven't seen a ad there since: Anyway, we seem to have gotten way off topic here! :) |
I see that NoAdBlock updated their code and removed the detection, the cosmetic filter should be once again safe to use in a few days. |
Confirmed fixed now! :) |
When browsing itavisen.no, I get the following error message:
This despite the fact that I'm not using the 'uBlock Protector' extension.
Link:
http://itavisen.no/
Screenshot:
https://www.mediafire.com/convkey/1ef2/67dicb7v6644ccd6g.jpg
Active filters:
All of them, except for these:
(I'm also using some filters of my own, but disabling them didn't help)
OS:
Windows 8.1 Pro, x64
Browser:
Pale Moon v27.4.0, x64
uBlock Origin:
v1.13.8
The text was updated successfully, but these errors were encountered: