A JavaScript browser library fails due to an adblocker blacklisting 'beacon.js'

Re:A JavaScript browser library fails due to an adblocker bl... by chillydawg on Sunday July 09, 2017 @11:32AM (#14730169)

As one of an extremely large group of people who will never use that library but DO get protected from some ads and tracking by blacklisting beacon.js, I disagree that it's an issue with ad blockers.

The internet is a toxic place, to put it mildly, and if you're getting into any kind of public facing service on it, you need to know exactly what you're doing.

[ Parent | on HN ]

Re:A JavaScript browser library fails due to an adblocker bl... by Ajedi32 on Sunday July 09, 2017 @02:35PM (#14731018)

Wait, you're saying that a false positive in an ad blocker is _not_ an issue with the ad blocker? Of course it is! Blocking files based solely on their names is a brittle and error-prone way of doing things, and this false positive is a clear example of that.

[ Parent | on HN ]

Re:A JavaScript browser library fails due to an adblocker bl... by chillydawg on Monday July 10, 2017 @12:37PM (#14737476)

For sure it's a false positive and I wish it didn't happen. But it does happen and there's no way I'm ditching my ad blocker just because of some small number of false positives.

[ Parent | on HN ]

Re:A JavaScript browser library fails due to an adblocker bl... by vsund on Sunday July 09, 2017 @11:51AM (#14730287)

I totally agree with you, but I think adblockers could do better than just block all requests that have "beacon.js" in it. But yeah, I definitely prefer many protected users about one working library :)

There are so many possibilities to block content, I'm sure that we could do better with protecting users against tracking while ensuring that less content gets blocked false-positive.

[ Parent | on HN ]