Closed uBlock-user closed 6 years ago
redirector.googlevideo.com
is also blocked which breaks videos at https://animehub.ac/watch/tsukumogami-kashimasu-sub?ep=148300
You should vet all domains you're adding, having to experience breakage every now and then is not a pleasant experience and starts to become an annoyance.
Thanks for the feedback, added to whitelist, changes will be visible with the next update.
Suggestion: Add user override whitelist for certain domains.
Issues like this could be solved by adding line to the whitelist, while giving everyobdy who doesn't want to be tracked freedom from tacking.
If some tracking is acceptable to some people, that shouldn't be forced on those who want none when using a No Tracking add on.
On 10/12/2018 3:12 AM, Saitama wrote:
|redirector.googlevideo.com| is also blocked which breaks videos at https://animehub.ac/watch/tsukumogami-kashimasu-sub?ep=148300
You should vet all domains you're adding, having to experience breakage every now and then is not a pleasant experience.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/notracking/hosts-blocklists/issues/100#issuecomment-429243295, or mute the thread https://github.com/notifications/unsubscribe-auth/AMQZQhgFPu5ygLSkAj0zNAZQ0MXnaS0pks5ukE8DgaJpZM4XY8wA.
This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Issues like this could be solved by adding line to the whitelist
Whitelist is not used by users, so not a solution. Users rely on the blocklists and when a false positive gets entered and if the given one is a famous one, it starts creating an annoyance as the domain is used everywhere on the Internet.
If some tracking is acceptable to some people
redirector.googlevideo.com
has no tracking whatsoever, in fact the entire googlevideo.com
has nothing to do with tracking FYI same for s0.wp.com
This is not about tracking, this is about the false positives that get added every now and then. The only way such false positives don't make it to the list is by vetting each and every domain which gets added to the list, before adding them, no automated script is going to do that.
This is all about tracking and tradeoffs between privacy and webservices that have a crappy implementation (relying on external CDN's, url shortners font hosts etc..).
Anyone who wants to can easily whitelist induvidual hosts and domains in native dnsmasq. Just add a custom list to your config and make sure that the whitelist is loaded first. Instead of forwarding dns requests to 0.0.0.0
you can forward them to your own dns or something lik 1.1.1.1
This is all about tracking and tradeoffs between privacy and webservices
Using your list is not a tradeoff anybody signed onto, so no.
Anyone who wants to can easily whitelist induvidual hosts and domains in native dnsmasq. Just add a custom list to your config and make sure that the whitelist is loaded first.
But why do I have to do that in the first place ? Just to able to use your list ? Nope, not acceptable. Instead you shouldn't be overzealous and collect domains from an automated script. Nothing can replace a manual check which makes sure no false positive like your list have occurs.
I got false positives so many times from your list, that not only it's not worth reporting everytime, but also is actually a waste of my time and I finally decided to remove your list. You're not going to do manual check which I gathered from your last reply, so it's better I remove it and use a list where a maintainer actually cares to make sure false positives simply don't get into the list in the first place.
@notracking Breaks css and images on https://deadline.com/2017/11/flash-supergirl-ep-andrew-kreisberg-fired-sexual-harassment-allegations-1202216549/