Nemeski to Firefox@lemmy.ml • 19 days agoManifest V3 Updatesblog.mozilla.orgmessage-square8fedilinkarrow-up171arrow-down10
arrow-up171arrow-down1external-linkManifest V3 Updatesblog.mozilla.orgNemeski to Firefox@lemmy.ml • 19 days agomessage-square8fedilink
minus-squareSimon Müllerlink14•19 days agoManifest V3 changes capabilities and meta-data about extensions, including limiting lots of things that worsen the experience for AdBlock Users. Google’s “cookie replacement” is Ad Topics, which collects your browser history and puts it into categories, sending those categories to websites.
minus-square@Vincent@feddit.nllinkfedilink18•edit-219 days ago including limiting lots of things that worsen the experience for AdBlock Users That is the Chrome implementation; Firefox doesn’t and won’t impose those limits.
minus-squareSimon Müllerlink13•18 days agoAs per the MV3 Specification, it is supposed to remove some APIs. Firefox included them anyways cuz they’re not assholes.
minus-square@Vincent@feddit.nllinkfedilink4•18 days agoI think there’s multiple specifications at this point. There’s Chrome describing what they’re doing unilaterally, and then there’s the WebExtension working group that’s trying to get alignment among several browsers.
Manifest V3 changes capabilities and meta-data about extensions, including limiting lots of things that worsen the experience for AdBlock Users.
Google’s “cookie replacement” is Ad Topics, which collects your browser history and puts it into categories, sending those categories to websites.
That is the Chrome implementation; Firefox doesn’t and won’t impose those limits.
As per the MV3 Specification, it is supposed to remove some APIs.
Firefox included them anyways cuz they’re not assholes.
I think there’s multiple specifications at this point. There’s Chrome describing what they’re doing unilaterally, and then there’s the WebExtension working group that’s trying to get alignment among several browsers.