1065
Google Chrome’s plan to limit ad blocking extensions kicks off next week (arstechnica.com)
submitted 2 years ago by to c/technology@lemmy.world
357 comments fedilink hide all child comments
 

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.
you are viewing a single comment's thread
view the rest of the comments
[–] 21 points 2 years ago (1 child)

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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 years ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 0 points 2 years 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.

  • permalink
  • fedilink
  • source
  • parent