• Septian
    link
    fedilink
    English
    37 months ago

    So, I keep meaning to look into this but I come from the wrong background to have an intuitive grasp of the pieces at play here. My work is primarily in back end systems development for data driven models and I have very little understanding of how networking elements interact or even what they are, for the most part. If someone with that background is reading these comments and willing to take the time, would you be able to provide an explanation for the differences between Manifest V2/V3 and how V3 prevents ad blockers from working?

    • Madis
      link
      fedilink
      English
      15
      edit-2
      7 months ago

      With manifest v2, extensions could block the content however they wanted, reading and modifying DOM as they see fit.

      Google claims that it is a security risk, so with manifest v3, extensions can only create and give the browser rules and the browser itself will block content based on them. The rules have a limit in size and capabilities.

      If that was still not clear, try thinking of unrestricted SQL access vs a UI for modifying a database.

      • Septian
        link
        fedilink
        English
        97 months ago

        Got it, that makes sense. Thanks for taking the time to write this up!

    • @AProfessional@lemmy.world
      link
      fedilink
      English
      5
      edit-2
      7 months ago

      The webRequest API allowed intercepting any network request in v2. Firefox also has an api for dns resolving. Lastly chrome now has a limited size for content blocking rules. All adding up to more limited blocking.