• Septian@lemmy.zip
    link
    fedilink
    English
    arrow-up
    1
    ·
    4 个月前

    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@lemm.ee
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      4 个月前

      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.

    • lengau@midwest.social
      link
      fedilink
      English
      arrow-up
      0
      ·
      4 个月前

      I use Firefox as my daily browser, but I tried the manifest v3 based uBlock experiment in Chrome and honestly I couldn’t tell the difference between it and the regular uBlock.

      I welcome people switching over, but I don’t think this is anywhere near the killing blow to adblocking people think it is.

      • umbrella@lemmy.ml
        link
        fedilink
        English
        arrow-up
        1
        ·
        4 个月前

        it is. it wont be updated as often, and ads will slip in between them. it also won’t be able to block as many trackers because the api is more limited.