> The Firefox version of uBO makes use of WebAssembly code for core filtering code paths. This is not the case with Chromium-based browsers because this would require an extra permission in the extension manifest which could cause friction when publishing the extension in the Chrome Web Store.
Anyone know what this extra permission is and why requesting this extra permission would cause friction?
Anyone know what this extra permission is and why requesting this extra permission would cause friction?