Comment by DanielBMarkham | Hacker News Reader

Comment by DanielBMarkham | Hacker News Reader

Wonder how the folks back at Comcast HQ would feel if the rest of the internet started adding messages to their web browsing telling them this kind of thing is unsatisfactory? Hey, this content injection game is a game that we all can play.

This is the old "windows alert" nonsense. Everybody and their brother that touched the windows system thought the user would want a popup when their program did something. So the user experience was/is full of annoying popups, warnings, and information messages. Log onto a heavily-customized windows machine that hasn't been used in a month or two and it's like visiting Los Vegas. Good luck trying to get anything done.

Comcast. All kinds of other internet providers manage to communicate these things to their subscribers without this nonsense. Take a hint.

Interestingly it would be easy to write some code that detected THIS code. Get web developers to add it to their sites and make it show a message that comcast are charging them for traffic they're causing. And then link to the class action.

inject.ly isn't registered (yet) so let's presume some enterprising HN reader uses that.

As a web dev, all I need to do is <script src="//inject.ly/detect.js"></script> and it will detect this (and any future variant) ISP injected content.

Extra points for someone implementing this to have it optionally make a JS call to another function or inject a customisable HTML widget on the page.

Or just make it a browser extension.

Browser extension would require action from end-users, making educating them using it rather redundant. Doing detection in JS can easily be deployed on servers with minimal work needed, and can potentially reach a very wide audience.

I was suggesting a browser extension to undo the mangling once users are educated. I must have misunderstood the original idea.

Do this!

Don't we just all need to put an appropriate JSON payload into '/e8f6b078-0f35-11de-85c5-efc5ef23aa1f/aupm/notify.do?dispatch=checkBulletin' on every web server we control?

;-)

The URI seems to be dynamically generated. But, yeah, we can write some rewrite rules and serve the requests.

If I'm not wrong, this is implementation of JSONP to avoid cross-domain AJAX request block, right?

Reply on news.ycombinator.com