[fChk]

For me I do not use adblockers much.When a website displays ads that were too annoying I often report the.ad covering content to make it disappear.(..................)

Interesting!.. Because I'm the anti-AD guy on the Web!.. Never used them on my own websites nor allow them to show up when browsing the Web.

In the pre-WebApp era (the era when JavaScript played a passive role), blocking ADs was as simple as using :
> a generic AD-blocker which use a pre-built database of well-known AD-servers, OR
> a simple Cross-site origin blocker that blindly block any third-party assets loading from another origin than the one initially loaded.

Then, in the post-WebApp era, things got complicated given that one needs to activate JavaScript for the website to load in the first place thus allowing the website owner to check for the presence of any AD-blocker before loading the website itself.

In this case, I generally resort to:
> just drop the whole thing and close the tab if I don't really need the website info, OR
> Use my WebDev skills to kill the JavaScript code that blocks the loading on the fly.

My bottom line hereis this: serving ADs should never be compulsory on the Web. Webmasters have the right to include them in their websites BUT WebUsers MUST also have the right to refuse them without being blocked from the website. A large portion of websites still function along this model -which is commendable- but an increasing portion is shifting to that unhealthy mandatory AD-driven Web experience model, as @deanhills complained in the OP.