4 ms·

Isn't the biggest problem with MV3 the 5000 rule limit? Or are there ways around that by compiling it into something internal? This is how adguard did it: htt

• SquareWheel 4y ago
  The current limit is 30,000 rules, but they've talked about raising it further beyond that point.
  • hombre_fatal 4y ago
    Trivia: 1Blocker convinced apple to raise the limit from 50k to 150k per list for Safari content blockers.
    • novok 4y ago
      My question is why have limits
      • hombre_fatal 4y ago
        Unbounded lists rarely seems like a thoughtful way to start out. But there are probably some DX and UX improvements over unbounded lists. e.g. recompilation takes time, so you set up developers for better UX when their dynamic lists are shorter and separate from their static lists, and they can compile multiple lists at once. (A 50k rule list took seconds on my old Macbook Air). Also encourages breaking lists into logical sublists which is better UX (e.g. regional lists) Also might discourage append-only accumulation where there’s no real incentive to prune the list (i.e. see EasyList). Some limit can help here. Kind of like deciding on a queue size vs unbounded: makes sense to set a limit, see who hits it, and cross that bridge as needed. In Apples case, they 3x’d the limit after a real world product made a real world case. Just some thoughts having built my own Safari content blocker.
        • novok 4y ago
          The entire living under the grace of the vendor-king to have permission to modify your own experience is fairly onerous on it's own. And before you say, but app store review!, I also think that is bad too.
• mirashii 4y ago
  > Isn't the biggest problem with MV3 the 5000 rule limit? Not really, the bigger problems come from the removal without alternative of a number of useful primitives that uBlock Origin used for blocking. See https://github.com/uBlockOrigin/uBlock-issues/issues/338 https://github.com/uBlockOrigin/uBlock-issues/issues/338 for a detailed accounting of the changes and their impacts.
• tssva 4y ago
  "It won't work on mobile anyway, only Firefox supports ublock origin on mobile?" Kiwi Browser which is chromium based supports Chrome extensions including ublock origin on Android devices.
• groovybits 4y ago
  > I'd suggest stop trying to support chrome and let it die? You're living in a bubble. If the extension doesn't support Chrome, its the extension that dies, not Chrome.
• staticassertion 4y ago
  If no one were building an adblocker for Chrome I'd just build it myself. I'm sure I'd do a worse job than the people doing it today but it'd be better than nothing.
  • hombre_fatal 4y ago
    Also, there are other adblockers on Chrome. They just aren’t as good and are sketchier. By pulling the extension you just enrich worse actors at the expense of innocent users.
• novok 4y ago
  Brave iOS has a built in adblock that I find about as good as ublock, compared to the ineffective iOS native safari style that MV3 forces you into. So the future for chromium browser based adblock are small mini-forks that re-add the proper hooks needed to implement adblock properly