Replies: 2 comments 1 reply
-
see #2189 |
Beta Was this translation helpful? Give feedback.
0 replies
-
have you guys started working on mv3 version? only two months left before they stop supporting mv2 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In theory, AdNauseam on v3 manifest version should be based on uBlock Lite, which is the version of uBlock designed specifically for the v3 manifest. Documentation can be checked here, and discussion here.
uBlockOrigin/uBlock-issues#338 (comment)
This documentation is worth reading, the last part is somewhat concerning to us to understand if it is possible that we continue to be based on uBlock Origin or not for chrome users:
The issue is that AdNauseam would require Service Workers to in order to collect the ads, visit them, and "send" them to the AdVault. Perhaps if we want to have AdNauseam for v3 we would have to implement our own service worker not based on uBlock any longer.
In order to implement our own Service Worker, we would need to have close attention to the issue raised here:
Taken this into consideration it seems that our option would be to release a "lite" version of AdNauseam, largely based on UBOLite, in which we would have to make our own brand-new implementation of clicking and collecting, using UBOLite only as a baseline for general adBlocking.
For other browsers AdNauseam would work as it is, keeping track with uBlock Origin main implementations.
I am far from having complete understanding of uBlock as well as the new implications of the v3 manifest, so feel to add ideas to this discussion. Links to the issues related to v3 manifest will be added bellow.
Beta Was this translation helpful? Give feedback.
All reactions