|
|
|
|
|
by ninkendo
443 days ago
|
|
FWIW I have no problems (and see no ads) on the site running a pihole dns-based blocker on my network. In-browser blockers are interesting because they’re actually modifying the DOM, and any JavaScript which expects the DOM to have certain elements, and doesn’t handle them being missing, can cause these kinds of failures. Network-level blocking should at least cause the requests to the ad services to fail in the first place, which has a much higher likelihood of being a tested code path (ie. Not breaking the site just because a request failed.) Basically I’m not surprised that in-browser, DOM-manipulating ad blockers cause failures in a lot of sites’ JavaScript, and I wouldn’t necessarily chalk it up to maliciousness on Slashdot’s part. |
|