this post was submitted on 21 Nov 2023
262 points (93.7% liked)
Technology
59340 readers
5096 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 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
An extension having access to everything on every page you visit is a potential security issue.
Whether that's an acceptable risk for you in order to have an extension that blocks ads is another question.
Extensions by definition are a security issue. For that matter, so is being connected to the Internet in the case of a browser.
As far as I know, the plan for Manifest V3 only included removing blocking from the WebRequest API and extensions using WebRequest could still see whatever activity they are given permission to view.
Correct, and the reasoning for removing blocking was performance.
Wouldn’t loading the ads impact performance moreso than loading them? Not really a browser nerd so no idea it just seems like blocking a piece of content from loading outright would be less demanding than loading it.
How the WebRequest API works is:
This is slow and will always be. Their change to remove blocking makes steps 2-4 a copy of the data instead of a synchronous call.
Now an ad can be slower, just by more data or bad JS. But that isn’t Googles concern because they sell those ads.
Ahhhh gotcha, thanks!