6 ms·
Safari's (Webkit's) content blockers are even better imo. Declarative rules that get compiled. Can't intercept arbitrary requests with Javascript logic but I do
by hombre_fatal 8y ago
Safari's (Webkit's) content blockers are even better imo. Declarative rules that get compiled. Can't intercept arbitrary requests with Javascript logic but I don't think that's necessary. Though it makes something like uMatrix harder to implement.
- kevin_thibedeau 8y agoThere's still a need for something like the element zapper which can remove obstructing popups that aren't implemented in Javascript.
- hombre_fatal 8y agoThough you can implement this with the content blocker API. You add a rule to the rule list and recompile it, though it does come at the expense of UX and flexibility for sure.
- stephenr 8y agoWhich has been a part of Content Blockers since day 1.
- ameshkov 8y agoSafari content blocking API is abandoned since 2015 when it was introduced. It simply does not allow using advanced blocking techniques which were developed by Chrome/FF blockers during these years. It might be enough to handle most of the ads at the moment, but it fails miserably when a website uses any adblock circumvention.
- hombre_fatal 8y agoAt the same time, I merely will not use a website that is so hostile nor do I regularly encounter websites like that. uBlock Origin breaks in this way as well, and the only website I can even recall with this behavior was a shady movie-streaming site I was linked to. What do you mean by abandoned? I use it and it works for me daily.
- ameshkov 8y agoAdblock circumvention is a technique when a website reinjects and encrypts the ads when it detects that they were blocked. Kinda like what Facebook does. Most of the changes and improvements to modern ad blockers are to deal with this kind of ads. Not in Safari, though. Webkit devs did nothing to improve or extend the content blocking API. Not to say that it still imposes the ridiculous rules limitation - you can't have more than 50k rules in a list (while Easylist alone has more than 80k).
- scarface74 8y agoThat’s an easy one to get around. 1Blocker X has 10 sets of rules.
- hombre_fatal 8y agoI'm not sure what misunderstanding you think I have with regard to adblock circumvention. I can appreciate that uBlock Origin wants to be a universal condom that works on every website for everyone, but I also don't think it's so damning if the content blocker API is sufficient for that. Yet uBlock Origin and its rule lists still fail at this task as well. A website can do any number of annoying things that uBlock Origin cannot block including things that aren't even related to ads. I simply refuse to use such websites. In fact, I want to know that a website does these things rather than remain in blissful ignorance. I don't want to support such a website even with my viewership. I've built content blockers. The rule limit is circumvented by simply bundling multiple rule lists. Also, 80% of Easylist is crap anyways. The problem with Easylist and things like it is that they become append-only lists because nobody wants to go back and verify that rules still apply. Not to mention all the site-specific rules for sites you'll never visit because it was someone's random hobby horse. But you can absolutely encode Easylist across two content blocker extensions bundled in one app. But in doing so, you'll also realize how easy it is to prune so that it fits in one rule list, there are so many rules for garbage sites.
- ameshkov 8y ago> I can appreciate that uBlock Origin wants to be a universal condom that works on every website for everyone, but I also don't think it's so damning if the content blocker API is sufficient for that. Yet uBlock Origin and its rule lists still fail at this task as well. I'd say it is sufficient for 90% of the websites at the moment. My point is that this is not a constant value. Advertisers adapt and evolve, and content blockers need to do the same. > A website can do any number of annoying things that uBlock Origin cannot block including things that aren't even related to ads. I simply refuse to use such websites. In fact, I want to know that a website does these things rather than remain in blissful ignorance. I don't want to support such a website even with my viewership. This is indeed the best way to let site owners know that this approach is unacceptable. I wish everyone were doing the same. > The rule limit is circumvented by simply bundling multiple rule lists. Sure, but this is a workaround, quite an ugly one in fact. > Also, 80% of Easylist is crap anyways It does contain a lot of redundant rules, maybe 30% of it, but not 80% that's for sure. And what if I want to use more filter lists? The only thing I can do is use the multiple lists workaround. It is simply weird that nothing was done about this limitation in more than 3 years.
- stephenr 8y agoHow is it abandoned? Because the API doesn't change more often than I change my underwear? It works well, is efficient and ensures user privacy and safety (from the sort of issues being described in the article) and it gained new capabilities (forcing a HTTPS url) after launch. As for your specific claim, 1Blocker has an entire section of blocking rules to counter anti-adblock. Sure, if some site want's to be completely hostile to users, it may still show up. The little cross icon on the tab solves that issue pretty quickly.
- ameshkov 8y agoSo you are telling me that not changing the API in years despite numerous requests is a good thing? Well, I disagree. Regarding https, this change was made in 2015.
- bobthepanda 8y agoThere's a wide spectrum between "abandoned" and "totally up to date." Not everything is black and white.
- stephenr 8y agoWell it all depends what the requests are, doesn’t it. I’m sure some have requested the ability to run javascript, that doesn’t mean it’s a good idea to add that to the api.
- ameshkov 8y ago> Well it all depends what the requests are, doesn’t it. Oh, there are all sorts of them. From simple feature requests (like being able to distinguish fetch/xmlhttprequest) and bug reports (like that it considers requests to subdomains third-party) to something more complicated. The problem is that regardless of what's requested/reported, there is no reaction. > I’m sure some have requested the ability to run javascript, that doesn’t mean it’s a good idea to add that to the api. Desktop Safari allows extensions to run javascript, why would anyone want to make it a part of the content blocking API.
- fredsir 8y agoI wish there was something like uMatrix for Safari but using content blockers. Would really scratch an itch for me.
- bad_user 8y agoSafari’d content blockers are next to useless. Safari is really easy to beat by anti-ad-blocking technology, the only reason for why more publishers won’t do it is because they don’t want to piss off people, but as the minority of people using ad-blockers grows, they’ll get over that fear. Also FYI injecting scripts in webpages is the only way to prevent anti-ad-blocking from working.