Hacker News Reader

Comment by brokentone | Hacker News Reader

I'm getting a lot of requests on our servers for "/e8f6b078-0f35-11de-85c5-efc5ef23aa1f/aupm/notify.do" so I can confirm this is in production. I can also confirm they suck at JS.

View on HN

How about creating /e8f6b078-0f35-11de-85c5-efc5ef23aa1f/aupm/notify.do on your server to notify Comcast users about what their internet service provider is doing? If people started doing that en masse it could bring attention to the problem and with enough publicity get Comcast to reconsider JS injection.

I don't really understand the point of this, either. Couldn't they starting redirecting users to a static page somewhere if there were a real need for a "critical and time sensitive" alert? If the supposed alerts aren't critical enough to justify doing that, use email, IM, RSS or twitter, or even build a custom notification notification app.

Best idea ever! But, they'll probably prosecute who ever does it for some BS reason and sentence them to a term of 500 years

Welcome to the Patriot era.

Dont forget a $70,000 fine.

Per "violation". So, $70,000 times a a few million pageviews.

every 5000ms

Of course the alternative is for comcast users to get together and sue the company for running malicious code on their machines.

Considering the way the handle their customers (myself being one of them), they honestly wouldn't care.

How about putting a giant video file there? Or just embed this: https://www.youtube.com/watch?v=0ilMx7k7mso (language)

I thought I was going to be rick rolled, but that's good too.

Google occasionally will do this to let users searching for Google requests know that their browsing experienced is compromised.

I'm assuming you mean the browser detection using useragent right? What's the better way of doing it?

Feature detection, to start.

Reply on news.ycombinator.com