[kmlx]

yes, one of my clients was hit by this and i was tasked with solving the situation.

i had to create a ticket in a repo explaining why blocking a whole domain instead of a single subdomain was actually pretty bad. they approved it and reverted the change.

finding where exactly i had to open the ticket and what to write was a “down the rabbit hole” experience.

[pbhjpbhj]

Domains are cheap, don't serve content on an ad domain maybe?

Sounds like perhaps your task was to ensure a company's ads got through an adblocker?

[kmlx]

my task was to rectify an issue in one of these crowd sourced lists of ad servers.

they were blocking a whole domain instead of blocking the ad-serving subdomain.

the issue was rectified, the main domain was replaced by the ad-serving subdomain.

[hathawsh]

Still, as pbhjpbhj suggested, if I were publishing both content and ads, I would consider publishing the ads on a different domain (not just a subdomain) to reduce technical issues. Domains with ugly names are very cheap.

[kmlx]

of course, and this is a valid proposal. but that was outside the remit.

[__jonas]

You could be right but you are definitely jumping to a conclusion here.

The default lists used by uBlock for example include things like error tracking telemetry, Sentry for example.

I can see why people want to block that stuff (privacy) but it’s not exactly an “ad”