Beyond all the normal inferences of why you can't target spammers... there is one fundamental thing to note. There has yet to be a proven case, directly or indirectly, of email spam causing death.:)
Yeah, it costs people time, lots of money, and probably some hair; meanwhile someone profits from the exploits good and bad. Hell, that happens all over the place, not just here.
See this previous/. article
The case of the "who dun it" really doesn't matter in the end. This could have been any number of power companies in the MidWest. These unfortunate saps are the ones that got slapped first
I don't know about you, but the exclusion of full PAC (Proxy Auto-Configuration) support is a big negative for Netscape 6 and Mozilla. What was AOL/Netscape thinking in releasing this browser like this (one of many things that statement could apply to).
Many, MANY larger institutions (ISP's, corporations, educational facilities) use the PAC's to configure browsers across the board (since IE and NS 4.x both support the proxy standard completely). What is even more peculiar is that Netscape set the standard for the autoconfiguration syntax in the first place.
Reading bugzilla, it appears that much work has to be done in implementing how PAC's worked in the first place with regards to JS wrappers and functions (which most of the important ones are depreciated!). I find this a real issue and a big cause of the lack of adoption for these browsers.
Beyond all the normal inferences of why you can't target spammers... there is one fundamental thing to note. There has yet to be a proven case, directly or indirectly, of email spam causing death. :)
Yeah, it costs people time, lots of money, and probably some hair; meanwhile someone profits from the exploits good and bad. Hell, that happens all over the place, not just here.
See this previous /. article
The case of the "who dun it" really doesn't matter in the end. This could have been any number of power companies in the MidWest. These unfortunate saps are the ones that got slapped first
Actually, it's Jesus
Sure. I can confirm it. I work for Ford IT. :)
I don't know about you, but the exclusion of full PAC (Proxy Auto-Configuration) support is a big negative for Netscape 6 and Mozilla. What was AOL/Netscape thinking in releasing this browser like this (one of many things that statement could apply to).
e s/demo/proxy-live.html
8 0
Many, MANY larger institutions (ISP's, corporations, educational facilities) use the PAC's to configure browsers across the board (since IE and NS 4.x both support the proxy standard completely). What is even more peculiar is that Netscape set the standard for the autoconfiguration syntax in the first place.
Reading bugzilla, it appears that much work has to be done in implementing how PAC's worked in the first place with regards to JS wrappers and functions (which most of the important ones are depreciated!). I find this a real issue and a big cause of the lack of adoption for these browsers.
Relavant links:
http://www.mozilla.org/docs/netlib/pac.html
http://home.netscape.com/eng/mozilla/2.0/relnot
http://bugzilla.mozilla.org/show_bug.cgi?id=530