Technology

60047 readers

2866 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 2 years ago

MODERATORS

[email protected]

1062

Google Chrome’s plan to limit ad blocking extensions kicks off next week (arstechnica.com)

submitted 6 months ago by [email protected] to c/[email protected]

359 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

[–] [email protected] 8 points 6 months ago (2 children)

What about Apple's WebKit? Does it count?

[–] [email protected] 21 points 6 months ago (1 children)

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.

[–] [email protected] 2 points 6 months ago (1 children)

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.

[–] [email protected] 0 points 6 months ago* (last edited 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.

[–] [email protected] 7 points 6 months ago (3 children)

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.

[–] [email protected] 3 points 6 months ago

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

[–] [email protected] 1 points 6 months ago* (last edited 6 months ago)

They've been separate for over a decade, and even before that they were heavily customizing it. They're cousins, but absolutely not close enough at this point to be considered the same.

[–] brbposting 1 points 6 months ago (1 children)

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?

[–] [email protected] 1 points 6 months ago

I admit, I haven't really looked into it. It's possible Apple implemented new HTML/CSS/JS standards independently, but it's also possible that Apple continued to backport Google's changes. Unless they had a business goal of being independent (or NIH syndrome) I would guess that they'd do mostly the latter, but you'd have to go read the code to know for sure.

They are definitely still more related to each other than either is to Gecko (which is to say, not related at all), though.