Origin extensions

Both uBlock Origin and its smaller sibling, uBlock Origin Lite, are experiencing problems thanks to browser vendors that really ought to know better.Developer Raymond Hill, or gorhill on GitHub, is one of the biggest unsung heroes of the modern web. He's the man behind two of the leading browser extensions to block unwanted advertising, the classic uBlock Origin and its smaller, simpler relation, uBlock Origin Lite. They both do the same job in significantly different ways, so depending on your preferred browser, you now must make a choice.Gorhill reports on GitHub that an automated code review by Mozilla flagged problems with uBlock Origin Lite. As a result, he has pulled the add-on from Mozilla's extensions site. The extension's former page now just says "Oops! We can't find that page". You can still install it direct from GitHub, though. The good news is that the full-fat version, uBlock Origin, is still there, so you can choose that. Hill has a detailed explanation of why and how uBlock Origin works best on Firefox. It's a snag, though, if like The Reg FOSS desk you habitually run both Firefox and Chrome and wanted to keep both on the same ad blocker. That's because, as The Register warned back in August, Google's new Manifest V3 extensions system means the removal of Manifest V2 – upon which uBlock Origin depends. For now, it still works – this vulture is running Chrome version 130 and uBO is still functioning. It's still available on Google's web extensions

#1 Are there any alternatives? I'm back to seeing ads again on youtube and everywhere and I hate it. #2 Are there any alternatives? I'm back to seeing ads again on youtube and everywhere and I hate it. I don't know about Ublock specifically, but UBlock Origin works. When Safari first opens, you have to re-enable it in Safari Preferences as it gives a warning saying the extension was shut down because it slowed web page rendering. #3 my extensions are no longer there. Only some are. I guess Safari automatically removes the non compatible extensions.[doublepost=1528251507][/doublepost]Thanks, I never heard about Ublock Origins, but I got it and it works! Thanks a bunch! #4 my extensions are no longer there. Only some are. I guess Safari automatically removes the non compatible extensions.[doublepost=1528251507][/doublepost]Thanks, I never heard about Ublock Origins, but I got it and it works! Thanks a bunch! Apple did you a favor, lol. Ublock Origin is a vast improvement over Ublock. kemo macrumors 6502a nn88 macrumors regular #6 This isn't working for me either on Mojave Beta 10.14 on safari. I'm getting every ad possible on youtube. Not wipr.Not Adguard.Not unlock origin.None of them work. Gen macrumors 6502a #7 safari 12 disables ublock origins as it 'slows down safari.' however, you can just enable it again. safari > preferences > extensions > check the box next to uBlock Origin to enable it. nn88 macrumors regular #8 safari 12 disables ublock origins as it 'slows down safari.' however, you can just enable it again. safari > preferences > extensions > check the box next to uBlock Origin to enable it. STILL DOES NOT WORK ON YOUTUBE.Already did that. #9 Same issue as well. Github doesn't have an updated version of Ublock Origin yet. #10 Same issue as well. Github doesn't have an updated version of Ublock Origin yet. Specifically for Safari? #11 It completely removed all my extensions. I had to re-download them. I could not find uBlock anywhere so I installed uBlock Origin. I have no idea what the difference is, seems to be the same thing as far as I'm concerned. So fortunately that works again. I don't know what the hell Apple was thinking. At the very least they should warn you before installing that your extensions will be deleted so that you can cancel this stupid update before it's too late. #12 Specifically for Safari. Safari was

Ongoing COVID-19 pandemic, we decided to proactively add to the allowlist all the potentially affected extensions that have been detected by Chrome telemetry in earlier Chrome versions. (This excludes extensions where authors have contacted us to indicate that they have migrated to the new security model. We thank those authors for their efforts and help in keeping Chrome users secure.) We still plan to deprecate the CORB/CORS allowlist in Chrome 87 and therefore extensions should migrate the new security model as soon as possible.It is possible that some affected extensions have been missed by the Chrome telemetry pipeline. For example, to protect user privacy, only public Chrome Web Store extensions have been reported and the reports were discarded if they came from less than 50 unique clients. If you observe that an extension is broken in Chrome 85 because of CORS or CORB, then please reach out to us by opening a bug - we might be able to help by temporarily adding the extension to the allowlist until Chrome 87. As a reminder, the error messages to watch out for are:Cross-Origin Read Blocking (CORB) blocked cross-origin response with MIME type . See for more details.or:Access to fetch at ' from origin ' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.Best regards,Lukasz Anforowicz and the Chrome Security Architecture teamOn Monday, July 20, 2020

Allowlist in Chrome 87 and therefore extensions should migrate the new security model as soon as possible.It is possible that some affected extensions have been missed by the Chrome telemetry pipeline. For example, to protect user privacy, only public Chrome Web Store extensions have been reported and the reports were discarded if they came from less than 50 unique clients. If you observe that an extension is broken in Chrome 85 because of CORS or CORB, then please reach out to us by opening a bug - we might be able to help by temporarily adding the extension to the allowlist until Chrome 87. As a reminder, the error messages to watch out for are:Cross-Origin Read Blocking (CORB) blocked cross-origin response with MIME type . See for more details.or:Access to fetch at ' from origin ' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.Best regards,Lukasz Anforowicz and the Chrome Security Architecture teamJackie Hanunread,Aug 20, 2020, 12:11:38 PM8/20/20to Łukasz Anforowicz, Chromium Extensions, Charles Reis, Simeon Vincent, Devlin CroninJust thought of a thing, why those break changes or official announcements only post on this forum mixed with lots of other discussions?Two suggestions:setting up a dedicated announcement mailing list.Or email to all extension developers who has a paid CWS account, like the email "[Action Required] Revised Chrome Apps shut down plan"Hello,To further reduce disruption amid the

Google's latest Chrome update has disabled several widely used ad-blocking extensions, including uBlock Origin. This comes with the search giant moving to a new extension framework, Manifest V3. The update is being rolled out to improve security and privacy, but it has also removed key functionalities that ad blockers rely on.On Reddit and X (formerly Twitter), people reported Chrome disabling older extensions. A notification appears under the extensions tab in the browser's taskbar, informing users that the add-on has been turned off and is no longer supported.Manifest V3: Google's new extension frameworkManifest V3 is Google's updated standard for Chrome extensions. It aims to improve security, privacy and performance. The company states that the changes aim to reduce the risks of malicious extensions and limit potential data abuse. But the update also restricts the ability of extensions to modify web requests, a feature essential for ad blockers.Key extensions disabledAs Google phases out Manifest V2, Chrome users are seeing popular extensions, including uBlock Origin, become obsolete. Any extension that hasn't or cannot transition to Manifest V3 is being disabled, leaving users with limited alternatives, stated a report in the Verge.Impact on other browsersThe shift to Manifest V3 isn't limited to Chrome. Other Chromium-based browsers, such as Microsoft Edge, are also losing support for older extensions. Brave, a privacy-focused browser, has stated it can only provide limited support for Manifest V2 extensions once Google fully removes them from the Chrome Web Store, reported The Verge.Firefox and other browsers stand apartMozilla Firefox has said