this post was submitted on 11 Mar 2025
1416 points (99.4% liked)

Technology

65819 readers
4936 users here now

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


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Pamasich@kbin.earth 3 points 17 hours ago

I've read that too, but I still have the ability to add a custom list. It says initially, so I assumed they got around that issue by now, considering it isn't the case for me.

I technically use Edge which afaik still allows MV2, so in case the extension somehow implements both and defaults to mv2 if available, I've decided to install Chrome and get ABP there to test. Even in Chrome, the ability to add a custom list is still there. As are all the other features, like manual updating. With custom list I mean both the ability to add a list per URL, and the ability to add custom arbitrary rules directly.

I don't really see why element blocking wouldn't be possible or allowed under Manifest v3. Like, it's entirely client-side. Manifest never comes into play there.

What I can imagine is that custom lists might work that same way too, removing the ads from the page after they've already loaded rather than blocking the web request directly which is afaik how adblocking works in mv2. I can't tell you if that's the case or not.