this is my first post i've made under a name: anyway, i am no hacker but I like neat jacker tricks and i read BB at places like this to pick them up. i have windows '95 and i decided to go on my own anti-ad binge... so i editted/windows/host and aliased doubleclick.net to 127.0.0.1 for starters. under netscape, a page with a banner/etc from doubleclick keeps trying to load the banner and doesn't stop, making it a lot slower. it never finds it, but you have to cancel the page loading and that is a pain in the ass. it did this for other banners, like adclub.net, etc. under ie5, it worked, except for doubleclick.net and adforce.imgis.com, where i would get a full-page error. so i instead aliased those to 192.168.0.1, the internal network IP... i have an internal network. i don't know what would happen if i didn't, but since i do and i run winproxy, those banners would show up on the page (in ie5) saying "you do not have access to this page", an ie5 error. and that is fine with me. but in netscape, all banner locations that were aliased to 127.0.0.1 would screw up like i descibed earlier. so i instead aliased all of those (except doubleclick and adforce) to 255.255.255.255. This did not effect the end result in ie5, but it fixed the problem in netscape (4.5). For doubleclick and adforce, the banners appear as broken links. my question is: why did i have to link to my internal network for doubleclick and adforce and not the others? (remember, my technical understanding of all this is very limited)
Slashdot Mirror
I have this but my computer is too lame to run it smoothly. Please e-mail me if you are interested.
test test
this is my first post i've made under a name: anyway, i am no hacker but I like neat jacker tricks and i read BB at places like this to pick them up. i have windows '95 and i decided to go on my own anti-ad binge... so i editted /windows/host and aliased doubleclick.net to 127.0.0.1 for starters. under netscape, a page with a banner/etc from doubleclick keeps trying to load the banner and doesn't stop, making it a lot slower. it never finds it, but you have to cancel the page loading and that is a pain in the ass. it did this for other banners, like adclub.net, etc. under ie5, it worked, except for doubleclick.net and adforce.imgis.com, where i would get a full-page error. so i instead aliased those to 192.168.0.1, the internal network IP... i have an internal network. i don't know what would happen if i didn't, but since i do and i run winproxy, those banners would show up on the page (in ie5) saying "you do not have access to this page", an ie5 error. and that is fine with me. but in netscape, all banner locations that were aliased to 127.0.0.1 would screw up like i descibed earlier. so i instead aliased all of those (except doubleclick and adforce) to 255.255.255.255. This did not effect the end result in ie5, but it fixed the problem in netscape (4.5). For doubleclick and adforce, the banners appear as broken links. my question is: why did i have to link to my internal network for doubleclick and adforce and not the others? (remember, my technical understanding of all this is very limited)