Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
General Apps
AdGuard
AdGuard Manifest V3 Extension v0.3.12
Message
<blockquote data-quote="ForgottenSeer 97327" data-source="post: 1041255"><p>My Guess: It is an experimental version to develop a 'working' adblocker with the MV3 restrictions. Main focus was to get the filtering engine working. AdGuard moved the filtering engine outof their products (AG for Windows, AG DNS and AG extension). For what I understand from their blog this was a generic filtering engine capable of simple ABP filtering (which is quite a feat when you consider that at DNS level only host file blocking rules were possible). Next they also moved the advanced filtering rules (think of cosmetic filtering etc) to a Separate filtering engine and encapsulated them with their own API. The latter to move seamlessly from MV2 to MV3 API. </p><p></p><p>When MV3 updates, it is hard to say that it was only done for static filters update or real software update.</p></blockquote><p></p>
[QUOTE="ForgottenSeer 97327, post: 1041255"] My Guess: It is an experimental version to develop a 'working' adblocker with the MV3 restrictions. Main focus was to get the filtering engine working. AdGuard moved the filtering engine outof their products (AG for Windows, AG DNS and AG extension). For what I understand from their blog this was a generic filtering engine capable of simple ABP filtering (which is quite a feat when you consider that at DNS level only host file blocking rules were possible). Next they also moved the advanced filtering rules (think of cosmetic filtering etc) to a Separate filtering engine and encapsulated them with their own API. The latter to move seamlessly from MV2 to MV3 API. When MV3 updates, it is hard to say that it was only done for static filters update or real software update. [/QUOTE]
Insert quotes…
Verification
Post reply
Top
