Incorporated changes from both patches in the new repo: https://github.com/steinm/pxlib/pull/9
This can be closed as it was addressed in: https://github.com/steinm/pxlib/pull/7
Exception for AdAway.Org domain
I'm also having the same issue. SMPlayer Version: 18.6.0 (revision 9075) MPV Version: 0.23.0
Does this mean that all new bugs / feature requests and other activity should be posted to the BitBucket repo instead of this one?
Thanks. So, to sum it up: 1. adl.windows.com is considered to be intrusive 2. If blocking it might cause a failure in the process, users should either: a) temporary disable Privoxy b) set the exception rule in user.action themselves. If the first point is valid, I agree with point 2, it's only reasonable. Though I genuinly believed against point 1, that's why I opened this ticket. I appreciate your work nontheless.
Well, I think documenting the reason of each specific blocked host in Privoxy's action file is part of what makes it great. When I failed to do it correctly, I appreciate you took time to provide a template on how to submit tickets with structured data, so as you say, it won't be hard to either add or remove the rules. On another note, I believe pgl.yoyo.org provides some good findings, so I think if we can document each host's behavior and reason, it could be a good resource to expand Privoxy's...
Also, you can cross-reference these URLs with some known ad lists, for example: - https://pgl.yoyo.org/adservers/