I think that was because Google dropped the controversial part of it or something, idk for sure since I don’t even bother keeping up with web dev. There was the whole WEI stuff to make up for that…
Nah, Mozilla just won’t implement the arbitrary restriction that Google set for content/ad blocking. They’ll be 100% API compatible, without limiting how many blocking rules there can be, which is the only bad part about v3 (or really the deprecation of the unrestricted v2), as far as I’m aware.
one word manifest v3
Did you know Firefox has also adopted manifest V3.
I think that was because Google dropped the controversial part of it or something, idk for sure since I don’t even bother keeping up with web dev. There was the whole WEI stuff to make up for that…
Nah, Mozilla just won’t implement the arbitrary restriction that Google set for content/ad blocking. They’ll be 100% API compatible, without limiting how many blocking rules there can be, which is the only bad part about v3 (or really the deprecation of the unrestricted v2), as far as I’m aware.
Mozilla can also continue supporting v2 for as long as they like. And they can provide additional APIs, which they already do, which is why uBlock Origin is, in fact, already better on Firefox today: https://github.com/gorhill/uBlock/wiki/uBlock-Origin-works-best-on-Firefox
@[email protected] @[email protected]
oh no i didn’t know that seems like i live under a rock