Chrome's Manifest V3 transition is here. First up are warnings for any V2 extensions.

Reminder to switch browsers if you haven’t already!

  • Google Chrome is starting to phase out older, more capable ad blocking extensions in favor of the more limited Manifest V3 system.
  • The Manifest V3 system has been criticized by groups like the Electronic Frontier Foundation for restricting the capabilities of web extensions.
  • Google has made concessions to Manifest V3, but limitations on content filtering remain a source of skepticism and concern.
    • @[email protected]English
      46•4 months ago

      It’s still DNS level only, right? That wouldn’t stop YouTube ads, or remove annoyances.

    • @[email protected]English
      16•4 months ago

      You can block ads from being served to you.

      But the flip side is that the website developer can make a website that won’t function if it can’t load the ads being served.

      And most users are gonna want a functional website.

      • dual_sport_dork 🐧🗡️English
        6•4 months ago

        Somebody’s going to need to write a web site with a very, very compelling function to make me give enough of a shit to not just click away if it is deliberately coded to not work with Firefox/adblockers. Like, gives me a million dollars per page load functionality.

    • @HarriPoteroEnglish
      -3•4 months ago

      You sweet summer child.

      How long do you think Chrome will let DoH be opt-in?

      • @AlphaAutistEnglish
        14•4 months ago

        You sweet summer child

        How are they going to get past my firewall rules?

        • @HarriPoteroEnglish
          6•4 months ago

          The day they do their own DoH in-browser it is definitely up to them. It’s already opt-in if you want to see how well your pi-hole won’t work with it enabled.

          Next step is to do DoH by default, and finally making it compulsory.

          • @Spotlight7573English
            3•4 months ago

            Chrome already does have DoH enabled by default from what I can tell.

            https://support.google.com/chrome/answer/10468685

            By default, Secure DNS in Chrome is turned on in automatic mode. If Chrome has issues looking up a site in this mode, it’ll look up the site in the unencrypted mode.

          • AlbumEnglish
            1•4 months ago

            They can do it all they want but it won’t work…

            If I “opt in” it falls back to non doh immediately because using doh on my network is not up to Chrome.

            use-application-dns.net + nxdomain for any known doh provider

            I don’t use pihole but doh blocking works great on my network. It should work on a pihole tho it’s pretty basic stuff.

            If you can’t resolve the domain you can’t validate the TLS certificate.