And no, these are not their own ads, they proxy the requests from their own domain to the Yandex Direct ad network. Even worse, there is some evil javascript that tries even different non-sensical HTML element names to try to get past the blockers.
Visible impact on page: empty right sidebar
Blocked requests:
- https://mc.yandex.ru/metrika/watch.js
- https://counter.yadro.ru/hit?unique_data_here
- https://yandex.ru/ads/system/context.js
I do feel thankful that toolchains like that don't seem to be in widespread use yet.
First reason is the lack of trust. Or limited trust, if you prefer. That is, SomeCompany may trust AdProvider enough to include their ads in its website, but then again not trust them enough to bundle random external code with their own. Letting the user's browser load from different origins does give you some separation.
Then there's the separation of responsibilities. Say something does break -and not because of blocking-, having the code bundled together makes it very easy to start a game of passing the blame. "It works for us", "We're not doing anything weird", etc. And not only that. There's also the question of who pays for that downtime. SomeCompany is kept from earning money, will AdProvider compensate them? SomeCompany'll probably need to provide evidence that the problem comes from AdProvider.
On the other hand, some websites may already be doing a very similar thing... though it's likely just accidental. I mean, I have experienced a fair number of websites breaking when googleanalytics is blocked and I'd bet it's not intentional, just bad programming.
McDonald's ad? Replace it with a McD's Roach Sandwich ad. Facebook ad? Replace it with "Zuck causes Genocide".
We can fight back.