Comment Yes and no, mostly no. (Score 2) 618
While I find his preaching about the moral rightness of what he does, and our duty to endure whatever shit he wishes to shove in our faces to be deeply obnoxious; it would not entirely surprise me if this little experiment by the carriers ends up going...badly.
Ad-blocking at the client end('client end' includes routers, filtering appliances, etc. under user control, if the applicable network is large or geeky enough) is simply the right of the individual to run the software of their choice on their hardware, to best serve their interests, in action. Running a public HTTP server doesn't give you some special right to dictate how the output is formatted for display.
Ad-blocking at the carrier level, though, gets risky fast. Whenever an ISP starts deviating from 'dumb pipe' operation, you have to start worrying about whose interests are going to win out, and how dramatically. Especially risky if (as is the case with quite a few cellular companies and ISPs) they also have a side interest in advertising, consumer analytics, a media arm, or other properties that could benefit from a little traffic meddling. We've already seen some of the more obscure WISPs provide 'ad blocking', then inject their own ads over the originals, worst of both worlds.
Ad blocking is well and good(and, frankly, until the advertisers can clean up the ghastly security situation, they have no justification for whining. Ads are easily the most dangerous part of most parts of the web you'd admit to visiting in polite company); but anything that gives ISPs more control over traffic is to be watched with considerable concern. You don't think that a plan to stick it to google is going to stop at blocking google's ads, do you? Not when they could use their privileged position on the wire to achieve the same tracking and advertising that google actually has to offer attractive services to achieve...
Ad-blocking at the client end('client end' includes routers, filtering appliances, etc. under user control, if the applicable network is large or geeky enough) is simply the right of the individual to run the software of their choice on their hardware, to best serve their interests, in action. Running a public HTTP server doesn't give you some special right to dictate how the output is formatted for display.
Ad-blocking at the carrier level, though, gets risky fast. Whenever an ISP starts deviating from 'dumb pipe' operation, you have to start worrying about whose interests are going to win out, and how dramatically. Especially risky if (as is the case with quite a few cellular companies and ISPs) they also have a side interest in advertising, consumer analytics, a media arm, or other properties that could benefit from a little traffic meddling. We've already seen some of the more obscure WISPs provide 'ad blocking', then inject their own ads over the originals, worst of both worlds.
Ad blocking is well and good(and, frankly, until the advertisers can clean up the ghastly security situation, they have no justification for whining. Ads are easily the most dangerous part of most parts of the web you'd admit to visiting in polite company); but anything that gives ISPs more control over traffic is to be watched with considerable concern. You don't think that a plan to stick it to google is going to stop at blocking google's ads, do you? Not when they could use their privileged position on the wire to achieve the same tracking and advertising that google actually has to offer attractive services to achieve...