Facebook adds 5 divs, 9 spans and 30 CSS classes to every post in the timeline

This example is likely not specifically targeting ad blockers, but ad scrapers for transparency: https://www.propublica.org/article/facebook-blocks-ad-transp...

> Our tool recognized ads by searching for that word. Last year, Facebook added invisible letters to the HTML code of the site. So, to a computer, the word registered as “SpSonSsoSredS.”

That article also links to this tweet in that paragraph.

> We have collected more than 100,000 political ads in this way. But Facebook’s latest update blocks tools like ours from clicking on the “Why Am I Seeing This” menu.

> The company added code that prevents clicks generated by computers — including browser extensions — on just that one button. Web browsers make a distinction between a click generated by the computer and one generated by your mouse. Clicks from your mouse are marked “isTrusted“ and those generated by computer code are not.

You can patch the browser to make isTrusted configurable, or to set it unconditionally true.

That has to destroy accessibility. I mean, a human using a screen reader is nearly equivalent to a scraper, so the whole thing seems problematic.

In my opinion extensions should be able to synthesize clicks on behalf of the user where isTrusted=true from the perspective of web content.

Isn't a screen reader generally a third party program? Software like a browser has no idea if the click event comes from a local mouse or other software. Telling the difference between what type of software specifically, like RDP/VNC/TeamViewer, AutoIT/autoclicker, and accessibility software is even more improbable.

Ah, this explains why so many of my GreaseMonkey attempts didn't work!