• JohnDClay@sh.itjust.works
    link
    fedilink
    arrow-up
    15
    arrow-down
    4
    ·
    6 months ago

    Manifest v3 is the new cookie replacement in Chrome right? Is Firefox also adopting it? I think Google’s version helps them monopolize information collection and inhibit add blocking, I hope Firefox’s version doesn’t do that? What’s the benefit?

    • RandomGen1@lemm.ee
      link
      fedilink
      arrow-up
      48
      ·
      6 months ago

      Manifest v3 is about add-ons or extensions like ad blockers, grease monkey, etc. Manifest v3 gets rid of some features of Manifest v2 that will severely hamper ad blocking. Mozilla has committed to keeping manifest v2 support in addition to v3 as a bypass to this

    • MrSoup@lemmy.zip
      link
      fedilink
      arrow-up
      40
      ·
      6 months ago

      Firefox ALSO supports Manifest v3.

      What’s the benefit?

      To make extensions made for Chrome easily portable to Firefox.

    • Simon Müller
      link
      fedilink
      arrow-up
      14
      ·
      6 months ago

      Manifest V3 changes capabilities and meta-data about extensions, including limiting lots of things that worsen the experience for AdBlock Users.

      Google’s “cookie replacement” is Ad Topics, which collects your browser history and puts it into categories, sending those categories to websites.

      • Vincent@feddit.nl
        link
        fedilink
        arrow-up
        18
        ·
        edit-2
        6 months ago

        including limiting lots of things that worsen the experience for AdBlock Users

        That is the Chrome implementation; Firefox doesn’t and won’t impose those limits.

        • Simon Müller
          link
          fedilink
          arrow-up
          13
          ·
          6 months ago

          As per the MV3 Specification, it is supposed to remove some APIs.

          Firefox included them anyways cuz they’re not assholes.

          • Vincent@feddit.nl
            link
            fedilink
            arrow-up
            4
            ·
            6 months ago

            I think there’s multiple specifications at this point. There’s Chrome describing what they’re doing unilaterally, and then there’s the WebExtension working group that’s trying to get alignment among several browsers.