Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It would be nice if there was an easier way to find out ISP injections for the layperson who can't really use wireshark/proxy and data comparisons, or for technical people that just don't have the time.

This project had potential ( it detected torrent traffic shaping) but it seems to no longer be under dev. http://broadband.mpi-sws.org/transparency/results/

Also this is a good read and contains comcast traffic shaping info: https://www.eff.org/wp/detecting-packet-injection

ps. Who cares about the shit JavaScript, this discussion should be about detecting packet injection and shaping.



There is validity in scrutinizing the code quality as well.

I agree that the ethical discussion is likely the paramount concern here and should be discussed, but the code they're using floods the global namespace which in theory could actually degrade service for end-users (by potentially breaking commonly visited JS-powered sites that happen to use globals of the same name).

Its worth pointing out that it would take minimal effort to make this code not suck as much (wrapping it in a closure for a start). IMO it gives more context to the initiative on Comcast's part. No time, effort, or care was put into considering the ethical implications of this practice nor its practical effect on the end-user.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: