Good luck. I suspect in no time uBlock Origin will have found a way to remove the ad elements from the DOM, even if they are served directly with the html of facebook and not a 3rd party domain.
I think where ad-blockers will start to have problems is with the millions of lesser known sites. Once these publishers swap over to proxying ad-content through their own domains and using a handful of simple evasion tactics (random file name for the self hosted JS file that pulls in the ad, site specific pseudo-random DOM element names for the ad spaces, not using an obvious sub-domain to load proxied ad content from); stopping ads getting through is going to require a lot more effort than blacklisting a few ad-server domains.
Right now the usual defense seems to be "we just buy 'em", but that's going to be a lot less convincing once Forbes.com is actively serving malware from their own site.
Alternatively, as mentioned in another comment, proxying might mean simply installing a managed ad-server within the publisher's infrastructure. So from an end-user PoV it looks like it's coming from the publisher's server but in reality it's still being served from a third party managed box.
Other than proxying I can't see how advertisers and publishers solve the ad-block problem without completely rethinking how ads are bought,sold,tracked and delivered.
Proxying seems to be one of the lowest-friction ways for them to continue business as usual, security be damned.
Alternatively, advertisers could host a server on the site's domain. A subdomain or specific path would be easily blocked, but a random path wouldn't be, e.g. http://www.example.com/626164776F6C66/ with identifier generated randomly. Plenty of existing content already looks this way.
Basically if this happens I'm switching my career to stealing from ad networks for fun and profit.
Not sure what the solution would be for CPC/CPM - off the top of my head maybe a random CNAME that pointed to an ad-server controlled IP so they could cross-audit client IPs via a JS drop in file? Presumably ad-blockers would easily pick that up though.
And in HTTP/2.0 they'll just switch to pushing the ads out to you.
In either case they can't guarantee it'll get on the screen, but they assuredly can make sure you download the damned ads.
Long term browsers will become more and more closed, DRMed, protected and such so that people have much less control over how stuff is displayed on screen.
Tim Berners Lee would cry if we end up with 2 webs.
Do you know anyone who is doing this already?
Everyone will get their own personal AI stalker bot from the birth. I have such high hopes for humanity. When we at it maybe also replace politicians with AI, I'm sure they will do a better job than we mortals.
That's why I have been beefing up the DOM filtering code in the latest versions -- there are already sites doing this.
There is a lot of untapped potential with the new operators, I am waiting for opportunities to put them to test, and fine-tune them if needed.
> That's why I have been beefing up the DOM filtering code
Isn't it all done through CSS selectors? Could you share more?
How about leveraging other heuristics such as HTTP headers (response cookies for starters) or timing information?
If you can't filter on classes or id's, what else? Dom element ordering? Image size properties? Structure of ad text?
But you still have to identify features and use an algorithm that basically goes "users identify images with features A, B, and C as ads, and they identify images with features X, Y, and Z as not ads, so put positive weights on A, B, and C and negative weights on X, Y, and Z, and block anything with a negative enough score".
I'd love it if the infinite scrolling shit went away and I could look at tweets by last hour, last 12 hours, last 24 hours, etc, and then paginate by day after that.
You're not going to please everyone. Even people who will like it a month down the line will hate it when you first roll out the change. And we should you have to support (|feature|!) different websites?
Like or is being exploited based on genetical brain responses to like because of the result of the "quest for new information" ?
This behaviour is psychologically engineered to trigger more dopamine fueled hits and with it fueling site engagement.
I hope you don't like music, movies, amusement park rides, love, etc., because I have some bad news for you.
Which is apparently a usage pattern nobody at twitter gets.