> It's important to note that blocking ads is NOT theft. Don't fall for this creepy idea, which is the criminalisation of the inalienable right to privacy. This is something I've never actually focused on but it's wild the amount of people I've installed AdBlock and ublock for who think it's something nefarious.
[flagged]
Now, I get that you're probably coming at this from "But hosting costs money and advertising is a way to recuperate the cost, so visiting the site but blocking ads is leeching bandwidth from the host without providing value back in the form of ad revenue".
But this doesn't hold up. All the cards are held by the content provider. If they -actually- have a problem with this, they have ways to stop it.
1. A server will always serve a request. That's it's job. So there's some unavoidable up-front cost to being a server on the internet.
2. But once it gets the request, it might serve a response that executes client-side Javascript that detects that an ad-blocker is running. At this point the content provider has a decision. They could block the requester. For example, redirect to a "Disable your adblocker" page. Or even in extreme cases blacklist the IP the request came from (though practically this doesn't happen). Heck, if things devolved into an arms race around ad-blocking detection, you could probably detect this server-side with some mechanism around serving a request to a browser while at the same time issuing a request to an ad provider to see if they received a corresponding ad content request within a certain window and if not, you know the ad was effectively blocked.
Ultimately it's not an obligation to accept ads. It's the content provider's prerogative to decide to deny service to ad-blocking clients, but realistically most content providers want traffic even if it's not generating ad revenue because of those sweet engagement metrics. If they don't, they have the tools to stop serving those requests.