News

Vivaldi Developers Promise That Ad Blocking Will Continue to Work

The developers of the Vivaldi browser, which comes with a built-in ad and tracker blocker, assured that ad blocking will continue to work even after the final entry into force of Google Manifest V3, which defines the possibilities and limitations for extensions.

Let me remind you that we also wrote that Opera, Brave and Vivaldi will not impose advertising on users after Chromium update.

So far, Manifest V3 is extremely far from ideal, but very soon it will finally come into force. Developers have to reckon with this circumstance.

For example, the developers of the AdGuard ad blocker recently talked in detail about what the transition to Manifest V3 is fraught with at present, and what problems they had to face while creating a new version of the blocker. In short: there are not enough limits on filtering rules, the syntax of declarative rules is very limited, users cannot view filtering logs, and innovations cause performance problems.

Now the topic of the imminent “release” of Manifest V3 has also been touched upon by the developers of the Vivaldi browser, who have devoted a large post on the company’s blog to this problem.

Back in 2019, the Vivaldi team assured that they would give users a choice anyway. Back then, the developers wrote that there were many possible scenarios for reacting to the third version of the Google manifest, including even restoring API functionality, which the Vivaldi team had to do before.

According to the company now, the Vivaldi team intends to keep their word made a few years ago and keep their ad blocker, which was originally created as a response to the upcoming Manifest V3, working.

The engineers explain that even in the early stages of development, they made a number of “architectural decisions” in the blocker code that should support its functionality, regardless of the changes in Manifest V3. So, the Vivali blocker relies on both the webRequest from Manifest V2 and the new declarativeNetRequest, which has already been broken so many mines.

Of course, there is always the possibility that the underlying architecture of Chromium will change now or in the future, and we will have to do additional work to make everything work. [Our blocker] is designed so that Chromium/content embedders can interact with requests made through the Chromium network service in general. The basic idea is that requests from a web service go through a specific piece of code provided by the embedder that can inspect or modify the request at various stages, much like webRequest currently does.the developers say.

In general, developers are confident that with the departure of webRequest, this particular API will not become useless and will not disappear with it. There are several reasons for this, they say:

  1. webRequest doesn’t disappear completely. Only the ability to block requests disappears. So, at a minimum, there should be a mechanism for proxying requests from network services through extensions.
  2. declarativeNetRequest is currently built on top of webRequest. It is possible that it will be rebuilt later to handle blocking at a deeper level. If it ever does, it will use a new set of block handling hooks that the Vivaldi blocker should also use. But there doesn’t seem to be any reason for that yet.
  3. The ability to block webRequest remains for enterprise users (at least for now). Thus, all of the underlying code for the webRequest, including its blocking capabilities, must remain intact.

All this leads to a natural question, will it be possible to use other ad blockers in Vivaldi, especially given the mentioned nuance about corporate environments? The developers write that they cannot guarantee anything, but they promise that if there is at least some way to extend the performance of the webRequest, they will definitely consider it and try to apply it.

It’s important to note that blocker extensions often depend on other APIs that are removed in Manifest V3 (and are likely to be much more difficult to bring back). Therefore, there is no guarantee that simply keeping the webRequest blocking function will be sufficient, and no additional work will be required on the part of the maintainers of these extensions.Vivaldi engineers say.

At the end of their message, the browser developers summarize:

Because Vivaldi is built on top of Chromium, how we handle API changes depends on how Google implements its restrictions. We can assure you that no matter what restrictions Google adds, we will eventually try to remove them. Our mission will always be to give you a choice.
User Review
0 (0 votes)
Comments Rating 0 (0 reviews)
Daniel Zimmermann

Daniel Zimmermann has been writing on security and malware subjects for many years and has been working in the security industry for over 10 years. Daniel was educated at the Saarland University in Saarbrücken, Germany and currently lives in New York.

Recent Posts

Remove Weaxor Virus (.rox Files Ransomware)

Weaxor Virus Ransomware Weaxor mean a ransomware-type infection. Weaxor was elaborated particularly to encrypt all…

2 hours ago

Remove Adblockelite.xyz pop-up ads (Virus Removal Guide)

Adblockelite.xyz is a site that tries to trick you into subscribing to its browser notifications…

9 hours ago

Remove Appcloud-center pop-up ads (Virus Removal Guide)

Appcloud-center.com is a site that tries to trick you into subscribing to its browser notifications…

9 hours ago

Remove Groopheetex pop-up ads (Virus Removal Guide)

Groopheetex.com is a site that tries to force you into clik to its browser notifications…

9 hours ago

Remove Vidstreambox pop-up ads (Virus Removal Guide)

Vidstreambox.com is a domain that tries to force you into clik to its browser notifications…

9 hours ago

Remove Mac-uptodate pop-up ads (Virus Removal Guide)

Mac-uptodate.com is a domain that tries to trick you into clik to its browser notifications…

9 hours ago