3 ms·
It could be feasible to circumvent this "attack" by drawing posts and ads in canvas elements. But then again, the blocker could "look at the pixels". Basicall
by kolme 10y ago
It could be feasible to circumvent this "attack" by drawing posts and ads in canvas elements.
But then again, the blocker could "look at the pixels".
Basically, if a human can tell the difference, a piece of software will eventually be able too.
With DRM we had the "if you can see it, you can copy" law. Here might apply the corollary "If you can tell it apart, you can filter it out".
- ArchReaper 10y agoIt wouldn't even need to 'look at the pixels', it would only have to identify the appropriate canvas elements.
- kolme 10y agoI was thinking of canvas elements with no differences between them. Same size, same properties, random id. In such scenario you'd have to "look at the pixels". The contents are programatically rendered and they're not subject to DOM inspecting.
- ArchReaper 10y agoIf it became prevalent enough, then theoretically you could update the *block extensions to identify the javascript (or libraries) that are used to render the ads and nullify them. My guess is that actually implementing this kind of thing would not be worth the cost.