3 ms·
From the blockers side, this doesn't really help as domain filtering is just the first step, then dom elements, url fragments and finally HTML identifiers (like
by michaelbuckbee 11y ago
From the blockers side, this doesn't really help as domain filtering is just the first step, then dom elements, url fragments and finally HTML identifiers (like being a standard ad image size).
From the user privacy side it's also mixed as there are still large scale efforts to link up users across sites and devices.
- majewsky 11y agoDepends on the application. I'm using uMatrix and always allow all content (including JS) that's served from the same domain. The problem for me really is tracking and visual clutter, and I assume that a first-party ad will not track me across domains and likely integrate well within the page layout. I'm fully aware though that I'm not the mean audience for adblocking.
- dredmorbius 11y agouMatrix isn't an ad-blocker. It uses ... a matrix ... of domains/hosts and content types to determine what is or isn't allowed to be presented/fetched by a client. Dedicated ad-blockers, such as uBlock Origin, apply heuristics which are specifically tuned to advertising signals -- hosts, domains, and, as noted in parent to your post, various HTML and other entity clues to advertising content.
- majewsky 11y agoWell, even if it technically isn't an adblocker, it's a darn good one in practice. And it sets up domain blocking by default, probably using the same lists as uBlock Origin.
- dredmorbius 11y agoYes, it's useful. No, it's not specific.