this post was submitted on 24 Oct 2024
39 points (100.0% liked)

Technology

37739 readers
573 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
alyaza@beehaw.org
TheRtRevKaiser@beehaw.org
gyrfalcon@beehaw.org
rs5th@beehaw.org
coldredlight@beehaw.org
Los@beehaw.org
SemioticStandard@beehaw.org
TheRtRevKaiser@kbin.social
remington@beehaw.org
39
Vivaldi polishes its browser, adds a dashboard • The Register (www.theregister.com)
submitted 1 month ago by sabreW4K3@lazysoci.al to c/technology@beehaw.org
26 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] Corgana@startrek.website 1 points 4 weeks ago

I found a Vivaldi blog post on this topic from 2022: https://vivaldi.com/blog/manifest-v3-webrequest-and-ad-blockers/

Will the Vivaldi Ad Blocker be affected by the Manifest V3 changes?

I made some architectural choices early on that I believe should keep it functional, regardless of the Manifest V3 changes. Of course, there is always a possibility that the underlying Chromium architecture will change now or in the future, forcing us to do some extra work to keep this working. ​> Hopefully, a more in-depth description of the architecture and some of the facts surrounding the Manifest V3 changes should help to show why I believe that our implementation is safe for the time being.