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.
One can enter physically a theater and watch a movie without paying quote often. Depending on the timing and staff you may not be confronted for a long time or at all.
Does that mean theaters don't really care or obligate consumers to pay?
There is nuance because the behavior around physical spaces is well established by law and social norm. This is absolutely not true for the internet, as evidenced by this very debate.
If you will indulge the hypothetical, and we step back from the established social norms (people know you are expected to pay), who is responsible for making sure customers understand the need to pay? The theater. If the theater doesn't secure their doors and doesn't say anywhere "you must pay to enter," then it's a completely reasonable behavior for someone to enter and watch until they are asked to leave or pay. If they refuse to leave, they're trespassing. If they are told to pay before entering and they sneak in, this is clearly trespassing.
But this is not really the same thing as online advertising. Online advertising is more like, you ask them to deliver a DVD to your house, and the agreement is "we'll deliver the DVD if you also let us place a camera and microphone in your home to watch your reaction to the DVD." Then you allow the DVD in but refuse entry to the spy gear. It would be very problematic to try and force people to accept the spy gear, or prevent them from denying entry to the spy gear. It would lead to laws purposefully designed to deny people privacy and control over their own homes. A much better solution would be for the company to just not allow you to take the DVD unless you also take the spy gear and to create laws around that behavior if necessary.
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.