-
Notifications
You must be signed in to change notification settings - Fork 80
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
"This extension may soon no longer be supported" #3309
Comments
Is a new version of uBlock Origin planned? |
|
A temporary solution is to edit the registry |
Is it planned in the more distant future that uBO will undergo a cleaner and more functional conversion or adaptation of its basic version without going through the uBOL version or should this hypothesis be completely abandoned? |
What is not clean and not functional with the current version of uBO? |
Slightly offtopic here, but by blocking manifest V2 adblockers, Google/Youtube violates W3 regulation too: https://www.w3.org/TR/ethical-web-principles/#render |
Does anybody know how to do this in Linux and macOS? Setting the given preference in ~/Library/Preferences/org.chromium.Chromium.plist does nothing in Chromium on macOS, and the linked article gives even less of a clue as to how to do it in Linux… |
First of all, thank you very much for your work and for bringing us uBO and uBOL. You said, uBOL is a MV3 API-based content blocker. But maybe what users need is not a MV3 API-based content blocker, but uBO that can keep most of its functions working as much as possible when Google forces MV3. So I think the main question is whether to give those users up or try to bypass Google's restrictions.
Perhaps now it seems that this is not "impractical", turn on "developer mode" is easy. Compared to give uBO up or changing browsers. ( e.g. tampermonkey has switched to MV3 and guides users to do so ) It's time to think about this problem. Finally, I don't mean to offend, no matter what decision you make, I respect and understand, and thank you for your efforts. |
The problem of trying to "bypass" is having an unreliable and unstable extension. Watch the videos between ABP and uBOL when browser launch: https://github.com/uBlockOrigin/uBOL-home/wiki/Frequently-asked-questions-(FAQ)#is-ubo-lite-a-bad-faith-attempt-at-converting-ubo-to-mv3 And watch videos between Adguard MV3 and uBOL when browser launch: uBlockOrigin/uBOL-home#153 (comment)
And when those users experience the unreliability like above and complain the issues, should uBOL switch back to the reliable version to solve those issues? |
Yes, but ABP "using trickery to force their service worker to always be up and running", it is indeed unreliable and unstable.
Obviously, they are two different things. uBOL uses the new DNR API while uBO is its own JavaScript-based network filtering engine. |
Content blocker is not just userscript API. There are many issues that need to perform at higher stage, network level and need more stability than userscript. If you have codes that make the other functions work without sacrificing the reliability, make clear PRs and give clear examples of what those PRs solve. "Maybe" is not the solution. You can try implementing it yourself to see what the issue is there. Remember it's not just ABP doing that, Adguard also has to do it. It's not because they don't know about userscript API. |
I am not sure how much UBOL is an alternative to UBO if UBO is more effective at blocking unwanted content. For instance, if a user watches a video and an ad sneaks through when one uses UBOL, but the same ad would be blocked by UBO, then I would, as a user, prefer to use UBO, as UBOL would have failed me at blocking ads. So I am not even certain UBOL can be called an ad blocker if it can not block ads. Maybe the whole "I do not want any ad data on my computer" could be integrated more on the operating system level, at the least for Linux users. Can we block specific bytes that are ads? That is, like packets we can automatically drop? Then we would not even need a general content blocker on the level of the browser; Google can not be trusted since they maintain the code for the primary browser (chrome). At the least we can now clearly see that Manifest v3 is Google declaring war on ublock origin in general. |
That already exists (i.e. AdGuard for Windows), but it is difficult to do. Traffic is encrypted (AdGuard adds their own root certificate to intercept HTTPS traffic, which is not great in terms of security), and a lot is harder and hackier. uBlock Origin can use offical browser APIs to hide elements and inject JavaScript scriptlets, which are generally stable and reliable. Doing that with a native app is more difficult, and I would imagine there are edge cases where element hiding would fail or break websites due to incompatibilities and conflicts. |
See:
uBOL is not meant to be perfect alternative to uBO, see :
See: |
I appreciate the efforts made on uBOL and the goals stated in the FAQ. But I think there is still a question that is not explicitly answered there: Does uBOL attempt to replicate uBO as much as possible, given the restrictions of MV3? Or is it taking MV3 as an opportunity to discard some of the more complex functionality of uBO? In other words, is there a possibility for an ad blocker that is MV3 and also is more like uBO than uBOL is? Admittedly this is an abstract question and I don't have specific functionality in mind. |
Read: Is uBO Lite a bad faith attempt at converting uBO to MV3? If MV3 adds any best practice to improve their blocking capability, without sacrificing reliability and efficiency, uBOL will adapt it. |
Okay, I see an answer to my question there after looking again. Thanks.
(emphasis added) To be clear, this all sounds very reasonable to me and I think I'll be happy with uBOL. Just looking to understand. |
Not sure what the plans are for this extension going forward, but some Chrome browsers may want to remain behind or re-implement MV2 in their own way, which can continue to give this extension the capability to act unimpeded by Google's (intrusive) demands. I plea to you, @gorhill — continue Chrome development and keep a list of supported browsers. Your work will be respected by projects which don't respect Google's demands for MV2 to be excised. |
For macOS and Linux, you can refer to the links below:
The policy to set is |
Well, I believe at the OS level it would be possible via the classical semi-tedious |
That is an ancient & obsolete technology, it can't fully replace adblockers, see: It's like comparing a cap pistol to a real gun. |
Does this affect other Blink-based browsers? Or will uBlock Origin still work on them? Maybe the best solution is to migrate from Chrome to something else, for my primary browser? |
Prerequisites
I tried to reproduce the issue when...
Description
On the "ChromeWebStore" site I have a message saying this and it is also perpetually in my browser.
"This extension may soon no longer be available because it does not follow best practices for Chrome extensions."
I really like the extension and what it offers, so I'm going back to its developer to inform them if this is not already the case because I care about the future of the extension.
A specific URL where the issue occurs.
https://chromewebstore.google.com/detail/ublock-origin/cjpalhdlnbpafiamejdnhcphjbkeiagm
Steps to Reproduce
Expected behavior
Je sais pas quoi rajouter de plus
Actual behavior
Pareil
uBO version
1.58.0
Browser name and version
Chrome
Operating System and version
Windows 10
The text was updated successfully, but these errors were encountered: