> eventually evolving into something that we cannot escape?
What I think: if they find a way to block adblockers, we'll find a way to block the adblock blockers! It looks like a fight that will keep going on for some time. Until they make ads so good that they are indistinguishable from good content, then we'd won [1]
I now block the blockers naturally, just not following those pesky links. I would love some statistics for instance, from the times Forbes and others are in the top HN page before vs after they completely started blocking adblock.
I'm really not sure they're better than ads. They're certainly more deceiving.
As long as the web is based mostly on HTML, the blockers win.
Genius line.
Individuals are already trying to improve things within their own spheres, witness the static site movement. Many people using static sites are trying to output some form of "reduced HTML" (without popups etc.) but it's very informal. It would be nice if there was actually a RestrictedHTML document format they could target, if you're trying to start a movement it's important to have words for what you're doing.
Note that while you'd be dropping huge amounts of features from the current HTML+CSS+JS stack, there are some features you'd want to add as well. For instance, the source of a webpage not being included with the page itself is not really optimal. (Think of how few pages are written in HTML directly -- they're written in Markdown on LaTeX or something else and then compiled to HTML). It would be nice to have native support for "ctrl+click on part of the HTML and then be taken to the original source".
> Accelerated Mobile Pages are just like any other HTML page, but with a limited set of allowed technical functionality that is defined and governed by the open source AMP spec.
Sweeeet. Thanks for the tip!
I have looked at webassembly. Let them do whatever they want there, ultimately they still have to write the text in the clear either in the dom or in a canvas (and a canvas is really slow to write, especially on a mobile phone) and in either case as long as your code can run before theirs in the same javascript, you can redefine a few key built in functions (e.g document.createElement, document.getElementsByTagName) you can force their code to call your implementation of whatever functions they want to write the information with - and you can write their text elsewhere, or filter images or whatever you want. Webassembly makes their code more difficult to debug, but they still have to call the same javascript functions straight javascript does.
So adblockers won't become obsolete, but it is possible that it will no longer be enough just to filter the dom.
If webgl will be adopted widely enough, this might even look plausible for some.
I think I am getting what you are saying though, but functionally that would be the same as just rendering it server side and serve it as an image (if you write the pixels randomly you still have to use the correct coordinates) which is possible today, yet nobody is talking about doing that.
So as long as they are still going to be rendering text client-side we can filter it. The moment they are not, we will have to start analysing the image, which should be fairly straight forward (ads are going to be in a rectangular area at least 20x20 pixels; text is going to a lot smaller and in ugly shapes).
Advertisers make more money on profiling and tracking users than showing you ads.
If you aren't paying for your content, your content needs to pay for itself.
What if they find a way to ban ad-blocking? What if web becomes completely binary, somehow making ad-blockers obsolete?[1][2]
What do you think?
[1]: https://hacks.mozilla.org/2015/12/compiling-to-webassembly-i...
[2]: http://techcrunch.com/2015/06/17/google-microsoft-mozilla-an...