when I get some spare time,
I can take another look.

Ive been working on some of my other apps,
and right now, Im working on a new app

to be honest,
I haven't tested svg documents thoroughly (at least not recently)

but it is a valid defined type:
https://developer.apple.com/documentation/safariservices/creating_a_content_blocker

The default blocklist is a remnant of when I first made Minim, and was envisioning it as more of a media blocker - for low bandwidth situations...

svg documents weren't blocked by default in v4, as there was a bug in the way Minim was parsing the default list.

Ive just released v5.8 in my store with some contextual menus to enable/disable multiple apps at once:

The App Store version is waiting for review by Apple, but should be available later today

hmm,
no there's not....
ill fix that now

Perfect,
Thanks for all the feedback

thanks for the feedback, ill fix these later today

ive just released v5 on my server, and it has also been approved for the App Store.

ive just released v5, and its been approved for the App Store. So it should be available soonish

If others are interested in this I’ll look into it

I think I finally have a robust solution...
you set me on the right track with unless-top-url

Im working on v5 of Minim, which has this much better implementation.
I've also reworked the UI to be less confusing, and will be adding some rudimentary regex type support.

Perhaps also:
# Character to represent any digit character one time

Safari only accepts a subset of regex, but I guess Minim could potentially accept any regex that is supported by Safari.

Perhaps I should limit it to . And * characters initially for simplicity…..

But, would it be confusing if I had a different rule syntax than regular regex?
For example I use:

• * character to represent any character any number of times
• ? Character to represent any character one time

This would make it more approachable for everyone

And for reference:
https://webkit.org/blog/3476/content-blockers-first-look/
“Matching any character with “.”.
Matching ranges with the range syntax [a-b].
Quantifying expressions with “?”, “+” and “*”.
Groups with parenthesis.
It is possible to use the beginning of line (“^”) and end of line (“$”) marker but they are restricted to be the first and last character of the expression. For example, a pattern like “^bar$” is perfectly valid, while “(foo)?^bar$” causes a syntax error.”

That does make more sense.
I’ll look into this for an update

Currently the * prefix affects only subdomains.

Perhaps I should just accept regex…. I thought that may be too confusing for non techies. I guess I’ve created more confusion with the current implementation.

I’m working on version 5 now, which hopefully makes the UI at least less confusing. Perhaps I should also look at how domains are implemented.

It applies the rules from the first tab on the block rules tab to ALL domains NOT listed as an exception.

I am working on an update now that will (hopefully) remove all the confusion from the UI

@NickC said in Won't block 3rd party properly:

@SweetP Sadly, I think I found a bug

When adding www.youtube.com as an exception to default blocking rules, all third-party resources get loaded as well, despite explicit blocking in both Minim's default and the exceptions list.

I think this is unfortunately a limitation of the WebKit content blocking API

It looks as though you can load third party content via a first party script....

The only reliable way I could find to block all third party content on YouTube was to block all first and third party requests for the following domains:

• *doubleclick.net
• *ggpht.com
• *googleapis.com
• *gstatic.com
• *ytimg.com

in an update, ill remove the filter for adding domains to minim via the main app

@NickC said in Won't block 3rd party properly:

@SweetP Another bug, if you unblock by default all first-party resources, the generic block rule for first-party gets generated but with an empty array for resource-type which blocks all resources, thus completely preventing any page from loading.

good catch.
this is a simple fix, and it'll be in the next release

This is a good idea,
Eventually I’d like something like this.
But I don’t have plans just yet…

@NickC said in Won't block 3rd party properly:

@SweetP All seems to be working as expected. Thank you for doing this, Russell. With these changes Minim has become quite a fierce content blocker for Safari. Nothing quite like it.

That’s great,
Thanks for all the great feedback and suggestions.

v4.1.2 should be available now

@NickC said in Won't block 3rd party properly:

I think the default behaviour of stripping the www part when adding an exception to Minim is no longer valid with this new better handling of domain/subdomain separation. In essence, www is a subdomain and should be treated as such.

Ill look into this
as im also doing some www assumptions elsewhere in code.
but good points