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.
  • grue@lemmy.worldEnglish
    0·
    6 months ago

    There are effectively only two web browsers: Chrome and Firefox. Literally everything else, aside from some really niche things that can’t render modern webpages, is a fork of one of those two that uses the same rendering engine.

      • grue@lemmy.worldEnglish
        0·
        6 months ago

        Nope, it doesn’t count. The only reason Safari/WebKit isn’t considered a fork of Chrome/Blink is that Chrome/Blink is a fork of Safari/WebKit instead.

        • bdonvr@thelemmy.clubEnglish
          0·
          6 months ago

          I’m sure they’ve diverged enough for it to be pretty significant compared to the Chromium browsers

        • brbposting@sh.itjust.worksEnglish
          0·
          6 months ago

          So it wasn’t, like, forked hard enough that now after the years it counts as a different browser? Expect it to render pages ‘n’ stuff pretty much like Chrome?

      • barsoap@lemm.eeEnglish
        0·
        6 months ago

        You mean KHMTL, born in KDE’s Konqueror. That spawned WebKit (Safari), that spawned Blink (Chrome, Edge, Opera, etc). The whole thing then finally came full-circle when Konqueror dropped KHTML due to lack of development, now you have the choice between WebKit and Blink (via Qt WebEngine).

        Then there’s Gecko (Firefox) and Servo which had a near-death experience after Mozilla integrated half of it into Gecko but by now development is alive and kicking again. Oh and then there’s lynx, using libwww, tracing its lineage back straight to Tim Berners Lee.

        • ripcord@lemmy.worldEnglish
          0·
          6 months ago

          No, they don’t mean KHTML. KHTML is an ancestor of WebKit and Blink, but WebKit forked from it over 2 decades ago. They meant WebKit.

          • barsoap@lemm.eeEnglish
            0·
            6 months ago

            They also didn’t mean lynx and yet I mentioned it. How come? Might the distinct possibility exist that I used the opportunity to draw a wider picture, and “you mean X” has to be understood as internet brain-rot rhetorics, not literally?

            Just a suggestion.

    • PopOfAfrica@lemmy.worldEnglish
      0·
      6 months ago

      Not to toot the kagi Horn, but they are talking about releasing thier webkit based Orion Browser on Linux. Ive been following that one closely since it has firefox extension support.

      • breakingcups@lemmy.worldEnglish
        0·
        6 months ago

        I’ve become very skeptical of anything Kagi, wishing they’d just focused on making one thing good instead of getting distracted by mediocre AI and a browser they can’t realistically support while their search is still subpar. Illusions of grandeur.

      • grue@lemmy.worldEnglish
        0·
        6 months ago

        I mean, if folks really want something like that, I’d say they shouldn’t have let KDE’s KHTML (which is what WebKit was forked from) die. But as I’ve said elsewhere in this thread, KHTML→WebKit→Blink are related and thus fail to combat Google’s web hegemony the way that Gecko (Firefox) does.