Nemeski to [email protected]English • 1 year agoGoogle Chrome warns uBlock Origin may soon be disabledwww.bleepingcomputer.commessage-square446arrow-up11.03Kcross-posted to: [email protected][email protected]
arrow-up11.02Kexternal-linkGoogle Chrome warns uBlock Origin may soon be disabledwww.bleepingcomputer.comNemeski to [email protected]English • 1 year agomessage-square446cross-posted to: [email protected][email protected]
minus-square@[email protected]linkfedilinkEnglish10•1 year agoThere is already a “lite” version of uBlock origin that conforms to the new manifest and will still work. There are still a few features missing, some can’t be implemented but others will be.
minus-square@[email protected]linkfedilinkEnglish3•1 year agoIs it by the same author? Nik Rols, iirc?
minus-square@[email protected]linkfedilinkEnglish14•1 year agoRaymond Hill (gorhill) is the author of uBlock Origin, uBlock Origin Lite, uMatrix etc.
minus-squareAxumlinkfedilinkEnglish3•1 year agoThe ‘block element’ picker is the big one that can not be implemented in the lite version. Also included block lists can’t update unless the extension itself updates.
minus-square@[email protected]linkfedilinkEnglish1•edit-21 year agoThose seem like really big hurdles. How can those be worked around? Is it not possible to trigger a manual block list update?
minus-squareAxumlinkfedilinkEnglish1•1 year agoIt’s not something that can be worked around. It’s specifically a design feature of manifest v3 to restrict these types of things. Your options are to accept this or use a different browser.
There is already a “lite” version of uBlock origin that conforms to the new manifest and will still work.
There are still a few features missing, some can’t be implemented but others will be.
Is it by the same author? Nik Rols, iirc?
Raymond Hill (gorhill) is the author of uBlock Origin, uBlock Origin Lite, uMatrix etc.
I remembered… poorly.
The ‘block element’ picker is the big one that can not be implemented in the lite version.
Also included block lists can’t update unless the extension itself updates.
Those seem like really big hurdles. How can those be worked around?
Is it not possible to trigger a manual block list update?
It’s not something that can be worked around. It’s specifically a design feature of manifest v3 to restrict these types of things.
Your options are to accept this or use a different browser.