3 ms·
> has about a half dozen extensions that load into Safari That’s because there’s a limit on the number of filters per extension. uBO may eventually need to do
by rafram 1y ago
> has about a half dozen extensions that load into Safari
That’s because there’s a limit on the number of filters per extension. uBO may eventually need to do the same.
- al_borland 1y agoInteresting... https://adguard.com/kb/adguard-for-safari/solving-problems/rule-limit/ https://adguard.com/kb/adguard-for-safari/solving-problems/r... Sounds like I should direct a portion of my ire toward Apple on this.
- bigyabai 1y agoAbsolutely not. They are trying to protect you, can you imagine how awful Safari would be if it let you sideload such nasty extensions? It would be just like Chrome, absolutely no market variation to speak of! Despicable. It's really AdGuard's fault for failing to fit their functionality within the arbitrary constraints Apple decided was suitable for a runtime.
- TingPing 1y agoIt is not an arbitrary decision. For one Safari compiles block lists to perform better, but it can be noticed at startup for big lists. Then there is just resource constraints since the focus is mobile. Chrome on mobile notably supports no extensions. But I do wish desktop Safari was more lenient.
- bigyabai 1y agoChrome's decision is also entirely arbitrary, so it's not a great example. Firefox on mobile notable supports Chrome extensions, without any real issues or battery drain whatsoever.