Google’s Chrome extension cull hits more uBlock Origin users - USE FUCKING BRAVE

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
Google is disabling the original uBlock Origin ad blocker for more Chrome browser users, alongside other extensions that are no longer supported as the browser migrates to its new extension specification, Manifest V3. According to Google, the new standard aims to improve privacy and security, but also removes a feature that some ad blocking extensions relied on to work — a compromise that Mozilla is unwilling to make for its own Firefox browser.

Users online are reporting on Reddit and X that Chrome is removing outdated extensions. In Chrome, a notification window will appear underneath the extensions tab on the browser taskbar with a message encouraging users to remove the impacted add-on, saying it has been turned off and is “no longer supported.” Two buttons are available that allow users to either quickly delete or manage their extensions.

Google’s uBlock Origin phaseout on Chromium-based browsers began in October, but started to have a wider impact in recent weeks. Bleeping Computer has also reported that extensions on staffers devices are being turned off, and Verge staffers have seen similar updates on our own machines.

These changes come as Google migrates Chrome away from the now defunct Manifest V2 specification. Support is being killed not just for uBlock Origin, but for any extension that hasn’t (or is unable to) update to Manifest V3. uBlock Origin users can switch to uBlock Origin Lite, which has more limited filtering capabilities than its predecessor due to Manifest V3’s ad blocking restrictions.

Chrome won’t be the only service affected by the Manifest V3 rollout — other Chromium-based web browsers like Microsoft Edge are also losing V2 support and Brave says it can only offer “limited” support once all Manifest V2 items are removed from the Chrome Web Store. Mozilla says that Firefox will continue offering both extension specifications, however, potentially giving uBlock Origin users a new browser to relocate to.

Link
Archive
 
They can try to use the already existing web DRM standards (thanks Mozilla and W3C for that cuckening) to fuck you up. Making youtube simply not work on 3rd party players or non-google-sanctioned browsers. They are 1 click away from that, why don't they do it I don't know.
Forcing the United Nations or EU to ban the creation and usage of ADblockers is more than enough. They don't need this sort of underhanded move. Youtube is not the only part of the internet and sometimes ADs on places like Rule 34.xxx or Fandom are just as bad, if not even worse.

Bro, just use Firefox. Outside of a brief flirtation with Pale Moon before it got shitty, I've been using Firefox since like 2007. It works fine and it lets you block ads. The foundation has been infiltrated by trannies, but so has every tech company. If you want to use tech that hasn't been infiltrated by autistic trannies, your options are going to be extremely limited. Maybe stick to saying nigger on BBS.
Trannies are in the indie tech fronts. If you're looking for Google or Firefox they have Pajeets because the UN has legions of those to enforce for them.
 
That one yeah, but as far as combating ADblockers goes, Pajeets do the dirty work for most of the time.
My point was Firefox still allows ad blockers, but many people here have an aversion to Firefox because of trannies. However, they are working everywhere in tech anyway so it's kind of a moot point. I'm not sure what discussion you're trying to have with me here, to be honest. If there are pajeets at Firefox, they are not yet trying to stop you from using ad blockers. I'm not saying that will never happen, I'm just saying it's not happening right now.
 
Would people have an aversion to adblocking if they were told trannies exclusively develop Adblocking extensions?
There might be a small outliner. End of the day people use effective tools and don't concern themselves with the source.

If satan made the best hammer everyone would use it.
 
Since yesterday, if I try to log into Gmail with Brave, I get:
gmail.webp
Learn more
Try again works, but I have to press it every time to log in.

Will they disallow the use of any browser other than the approved ones for their sites?

Edit. From learn more:

Sign in with a supported browser
To help protect your account, Google doesn’t let you sign in from some browsers. Google might stop sign-ins from browsers that:
  • Don’t support JavaScript or have JavaScript turned off
  • Have unsecure or unsupported extensions added
  • Are being controlled through software automation rather than a human
  • Are embedded in a different application
 
Last edited:
  • Have unsecure or unsupported extensions added
Your browser might be reporting the extensions you have installed, which is used to fingerprint and track your browser. You can use extensions that help make your browser signature less unique, but sites will also forget who you are constantly requiring multiple relogs, 2fa, etc. But that should stop Google from blocking you simply based on the extensions you have installed.

 
Last edited:
Lmao. I've been there. This is where you be malicious about not being able to do certain tasks. Tell coworkers, clients, users, management, etc that you cannot do your job because the application requires is not within your scope of work. Refuse to do the job if they aren't supplying you with the proper tools. Don't tell them to their face that it's their fault. Simply say, "Well I can't help you with that because my application isn't currently working and I don't have the authority to change that. Sorry." Someone will budge sooner or later— and they can't write you up or get pissy about it because it's their fault. You're simply doing everything in your power and in your scope of work. This falls on your manager/director, not you. You're merely a peon following orders. Put in a work order and/or application request and CC your entire team- send it to management and send it up to director level. Let them fight amongst themselves.
Sympathetic middle management is letting us use petty cash for the subscription-based service which is funny because now they're still paying for it, just more because we're not getting the group discount or the added features that allow the higher ups see data so fuck em.
 
I could believe that. Leave it to Google to inform the unwashed Internet masses about what an adblock is while trying to stop them from using it.
I mean everyone I know uses one, it’s not that much of a stretch to assume that it’s finally starting to eat into their bottom line. I’ll never browse without one but it’s finally caught up to them.
 
For those who don't know, you can still force Chrome (for now) to make Ublock Origin (and other apps Chrome turned off) to work.

A Ublock origin dev posted the instructions (with a video) on Reddit. Here is a link: https://old.reddit.com/r/uBlockOrigin/comments/1lwztf1/ublockorigin_fully_disabled_on_chrome_now/

There are instructions on the link for potential support up to 142, which are a little more involved (using unpacked extensions, developer mode, etc.), but posting the basic instructions for 138-140 for reference:

On 138, set the flag:
chrome://flags/#temporary-unexpire-flags-m137[Enabled]
And restart Chrome again.

On Chrome 139, use the "unexpire 138" flag to access the remaining ones.
chrome://flags/#extension-manifest-v2-deprecation-warning[Disabled]
chrome://flags/#extension-manifest-v2-deprecation-disabled[Disabled]
chrome://flags/#extension-manifest-v2-deprecation-unsupported[Disabled]
chrome://flags/#allow-legacy-mv2-extensions[Enabled]

On Chrome 140 there will be no more flags to regain access.
You can set your chrome shortcut to this to regain access for a while longer, but it's unclear how long that's gonna work:
chrome.exe --disable-features=ExtensionManifestV2Unsupported,ExtensionManifestV2Disabled

I should note that I'm on 138 and still had to disable the flags for deprecation-disabled and deprecation-unsupported to get UBO back. In the process of migrating over to LibreWolf though
 
Last edited:
To help protect your account, Google doesn’t let you sign in from some browsers. Google might stop sign-ins from browsers that:
  • Don’t support JavaScript or have JavaScript turned off
  • Have unsecure or unsupported extensions added
where this would seem to be headed is toward some sort of Trusted Browser framework, cryptographically secured from hardware all the way up through the software stack, that guarantees (to the website developer) exactly how the stream of internet transmitted octets (HTTPS, HTML, or whatever) will be presented to the user. no reason to stop with "DRM" which secures only the presentation of audio and video streams.
 
The thing about that though is the things that really make a signature unique enough to identify a single user change to frequently to be used on its own. More persistent means have to be used.
Responded without comprehending; after re-reading I see you're talking about creating a walled garden.
 
Back