Google’s campaign against ad blockers across its services just got more aggressive. According to a report by PC World, the company has made some alterations to its extension support on Google Chrome.

Google Chrome recently changed its extension support from the Manifest V2 framework to the new Manifest V3 framework. The browser policy changes will impact one of the most popular adblockers (arguably), uBlock Origin.

The transition to the Manifest V3 framework means extensions like uBlock Origin can’t use remotely hosted code. According to Google, it “presents security risks by allowing unreviewed code to be executed in extensions.” The new policy changes will only allow an extension to execute JavaScript as part of its package.

Over 30 million Google Chrome users use uBlock Origin, but the tool will be automatically disabled soon via an update. Google will let users enable the feature via the settings for a limited period before it’s completely scrapped. From this point, users will be forced to switch to another browser or choose another ad blocker.

Archive link

              • CrypticCoffee@lemmy.ml
                link
                fedilink
                arrow-up
                1
                ·
                4 months ago

                It’s open source. You’re assuming this is telemetry without having an idea. Could be diagnostics, could be pocket, could be sync check.

                Without evidence, sounds like a load of FUD.

                It’s ironic you call me dense.

                • suction@lemmy.world
                  link
                  fedilink
                  arrow-up
                  1
                  arrow-down
                  1
                  ·
                  4 months ago

                  Diagnostics is just a nicer term for telemetry. And sorry for calling you dense, you’re clearly here to market Firefox, you’re just a bad guy.

                  • CrypticCoffee@lemmy.ml
                    link
                    fedilink
                    arrow-up
                    1
                    ·
                    4 months ago

                    No. It’s when bugs and crashes happen, and trying to identify how. Such as stack traces for example, or memory usage when an app keels over.

                    I’m not here to market FF, I’m here trying to counter balance the Firefox haters that spend so much hate to trash the only real legitimate chance we have of Google not dictating web standards. I don’t know why so many people shill for billion dollar companies. Do they love Google that much, or are they simply useful idiots?