Friday, June 12, 2015

Anti-Ad-Blocker: Following the Money

It wasted time while it reported saved bandwidth. The extension acted like another advertisement. Yesterday, web-browser developers released built-in content control that overrides extensions that block advertisements. Yes, the built-in version does the same as the extension except the newer release disabled insecure methods made available to the extension. One ad-blocker extension producer, that also advertises for support, "cried foul" over ruined revenue due to the newer built-in version. Each of us need food on the table for our families, so the argument is equal there. The younger generations, however, installed these kind of extensions like it is weird not to do it. Now, instead of magically explaining market metrics that only top CEOs know best to younger generations and convincing them to ethically unblock ads and uninstall the extensions, the built-in version put it front and center and made that argument null and void.
     Our argument was about "pop-up ads" and ads that are "all over the place." Google Chrome nicely demonstrated one way how built-in javascript performance blocked pop-up ads. It tracked real individual intervention down to each request for pop-up displays. It blocked pop-up events where no real individual initiated that event. That complicated web-development, but non-programmers paid scientists and engineers for this web-development and continually pay for further resolution of this kind of security without the argument.
     Engineers continually produced higher standards instead of continually wasting time while involving everybody else into the argument. With the built-in version, our argument followed the money down to the next level of justice. Where extensions once wasted time with supposedly unknown methods by anonymous intervention with random accounts, our argument is now focused on analysis of the built-in knowns with food on the table kept in-mind.