• ipkpjersi@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    6
    ·
    3 months ago

    Eventually Firefox will switch to V3 anyway so it’s kind of just delaying the inevitable.

    It sucks that this is the future of the Internet.

    • mint_tamas@lemmy.world
      link
      fedilink
      English
      arrow-up
      9
      ·
      3 months ago

      Manifest v3 is already supported in Firefox (they must support it to keep the extension ecosystem alive), but they implemented it without the user-hostile restrictions.

      • ipkpjersi@lemmy.ml
        link
        fedilink
        English
        arrow-up
        6
        ·
        edit-2
        3 months ago

        Oh, I wasn’t aware of that, I thought the user-hostile restrictions were inherent to Manifest v3 and they were unavoidable.

        Okay, maybe just maybe Firefox squeaks by unharmed then.

        edit: I literally just had someone else tell me just now that “It’s not something that can be worked around. It’s specifically a design feature of manifest v3 to restrict these types of things.”

        So which is it? I’m kind of getting mixed signals here.

        edit 2: Oh, it sounds like Google has additional arbitrary restrictions on content blocking functionality, beyond what Manifest V3 itself has.