Nemeski to Technology@lemmy.worldEnglish • 2 months agoGoogle Chrome warns uBlock Origin may soon be disabledwww.bleepingcomputer.commessage-square448fedilinkarrow-up11.03Karrow-down112cross-posted to: news@lemmy.linuxuserspace.showfirefox@lemmy.mlpiracy@lemmit.onlinepiracy@zerobytes.monstertechnology@lemmy.zipbrowsers@lemmy.ml
arrow-up11.02Karrow-down1external-linkGoogle Chrome warns uBlock Origin may soon be disabledwww.bleepingcomputer.comNemeski to Technology@lemmy.worldEnglish • 2 months agomessage-square448fedilinkcross-posted to: news@lemmy.linuxuserspace.showfirefox@lemmy.mlpiracy@lemmit.onlinepiracy@zerobytes.monstertechnology@lemmy.zipbrowsers@lemmy.ml
minus-square@ipkpjersi@lemmy.mllinkfedilinkEnglish1•edit-22 months 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•2 months 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.
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.