||sandcats.io/embed.js$script
view.gif?page=$image
Note that you would have to change the filters if the scripts and tracking pixel are renamed of course but this should catch a majority of the push button installs.
||sandcats.io/embed.js$script
view.gif?page=$image
Note that you would have to change the filters if the scripts and tracking pixel are renamed of course but this should catch a majority of the push button installs.
It also strikes me as an unwinnable battle for all but the largest sites.
Getting to first party hosting of more intrusive analytics (scroll location, etc) I think rather than disallowing certain scripts/URLs to run, you have to get back to behavioral-based blocking. Doing that in an environment that you allow any JS to execute seems tough since sandboxing something that can update the page based on location can "talk" to another part that can report back to the server.
If you don't like intrusive first party analytics, just stop all JS.