this post was submitted on 04 Oct 2024
1158 points (98.5% liked)

Technology

59030 readers
3030 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 another!
  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, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
 

Clearly, Google is serious about trying to oust ad blockers from its browser, or at least those extensions with fuller (V2) levels of functionality. One of the crucial twists with V3 is that it prevents the use of remotely hosted code – as a security measure – but this also means ad blockers can’t update their filter lists without going through Google’s review process. What does that mean? Way slower updates for said filters, which hampers the ability of the ad-blocking extension to keep up with the necessary changes to stay effective.

(This isn’t just about browsers, either, as the war on advert dodgers extends to YouTube, too, as we’ve seen in recent months).

At any rate, Google is playing with fire here somewhat – or Firefox, perhaps we should say – as this may be the shove some folks need to get them considering another of the best web browsers out there aside from Chrome. Mozilla, the maker of Firefox, has vowed to maintain support for V2 extensions, while introducing support for V3 alongside to give folks a choice (now there’s a radical idea).

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 5 points 4 weeks ago (2 children)

When new fearures added to V3, will Mozilla port it to V2 too?

[–] [email protected] 9 points 4 weeks ago

IIRC, they've said they'll implement V3 to maintain compatibility, but they'll also continue to maintain V2. You, the extension developer, will not be forced to use V3 if you don't want to.

[–] [email protected] 3 points 4 weeks ago (1 children)

educated guess: since firefox is implementing v3 support alongside their v2 extensions, there shouldn't be any issues running v2 and v3 extensions side by side in the foreseeable future

[–] [email protected] 4 points 4 weeks ago (1 children)

I think they are wondering if one extension can use both v2 and v3 APIs at once? As in whether v3 APIs will be "backported" to allow v2 extensions to use them

[–] [email protected] 1 points 4 weeks ago

I wonder how they'll solve that riddle.