And those users should be allowed to re-enable it. But it still should be blocked by default. And it definitely doesn't excuse Telewest for failing to cut off zombie hosts after receiving spam reports.
If an ISP does not block outbound 25 by default, and some of their customers are spam zombies, and they are notified about the offending PCs, and they don't stop the zombies, then that ISP is most definitely NOT the victim. Telewest is grossly negligent, therefore spam-supporting.
Preventing spam from your network is not just an afterthought or a courtesy, it is a RESPONSIBILITY. If you shirk it repeatedly, you should be held accountable.
That's the bottom line. They are cleaning up their act because their customers are complaining. Their customers are complaining because they are listed in SPEWS. They are listed in SPEWS because Telewest has been completely ignoring their spam zombie problem for a LONG time.
SPEWS WORKS. You may not like their methods, but they get results when other gentler attempts have failed.
As a long-time NANAer (heck, I supported its initial RFD/CFV) I can tell you that SPEWS has very simple rules, they follow those rules, and anyone who has argued with you about SPEWS is in fact NOT SPEWS.
If you are the directly-listed ISP, you kick every single indicated spam source off your network, make the relevant DNS/Whois changes, and post these facts to NANA*. Assuming you are not a repeat offender, you should be removed within days or even hours.
If you are a customer of the offending ISP, you either convince them to do #1 above, or leave them.
I would rather have Apple define "safe" properly and exclude anything capable of installing itself (or other files) outside of your designated download location.
Web page which drops a visible file on my desktop: not so bad.
Web page which adds anything to my Library folder: bad.
Yeah, government-created infrastructure is always a catastrophe. Like the national highway system, and municipal sewers, and 99% of the early internet, and... oh wait, those actually work pretty damn well.
But But But... look at how much better privately-run infrastructure works! For example, Comcast cable rarely goes down, customer service is prompt, and the costs are reasonable... no wait, those are all false.
I don't have municipal internet in my residential area. I don't need or want it, and there are no plans to install it. But if the citizens of some other town think it's a good idea, why the hell should there be a law that forbids them from trying?
MAPS stopped being a reputable service ever since they joined MFN/Abovenet. I say this as someone who previously supported MAPS and even donated to their legal defense fund.
It was quite sad to see them fall to the dark side. It's even sadder to see that MAPS is still in active use by anyone outside of MFN.
Would you honestly suggest that I should have to purchase every book in the library that I want to read
The US publishing lobbyists would say YES absolutely. In fact, they've been actively fighting against libraries (not to mention used book sellers) for several years. To them, the library system is just as "evil" as Kazaa.
The Lion King, like all standard animations, uses large swaths of relatively flat color punctuated by dark linework. Optimal compression for line art is substantially different from that of highly-shaded photographic imagery.
Given that the vast majority of video available on TV is real-world, that test case seems like a poor indicator for typical performance.
I don't understand how a DNS or network capacity problem could cause a web server to respond with an explicit "404
If you use MSIE with the default "friendly error messages", then pretty much ANY failure (code 404, no DNS, congestion timeout, etc) displays the same generic error (which is also the same as the default 404 page sent by IIS).
Which is why when I'm trying to diagnose a customer's complaint about our web site "not working", the first thing I do is have them turn off "friendly" error messages (followed by some casual buzz for Firefox).
They used to link to it at the bottom of some (random?) search result pages, but I haven't seen it posted publically in a while. Perhaps it didn't actually work as well as you or they hope it would.
The problem is that "P2P" is not monolithic, and each variation requires a different analogy. Things like Grokster were certainly intended to aid (illicit) media swapping, and their associated business entities don't help to dissuade this notion. OTOH we have stuff like BitTorrent, which has literally enourmous non-infringing uses (result #3 and similar notwithstanding).
Hmm...I'm having trouble here, what kind of blade is BitTorrent? Maybe a chainsaw powered by a beowulf cluster of tandem exercise bikes?
NOT in the same league as Einstein or Linus Torvalds
Funny that your parochial flamebait happens to be true. Ramanujan was definitively smarter than either of them.
Not to put down Big Al, but he only had a small armful of memorable discoveries spread over the decades of his career. OTOH, Ramanujan pumped out astonishingly brilliant stuff pretty much every day of his sadly brief adult life.
Plog is short for "plastic clog" (as in shoe). You'll see them quite often in hospitals because they're comfortable for standing and very easy to disinfect.
People have a right to be annoying in their own home, or office, or even in many public spaces. But when someone intrudes into my personal space (physical, email, phone, or otherwise) to be annoying, they better be prepared for a LARTing mallet.
I think the important distinction is that the second component of the value equation (believed to be O(n), log(n), or otherwise) is dependent not on the total size of the network, but on the size of the sub-network that each user KNOWS HOW TO ACCESS. This is affected not just by size, but by usability, metadata, etc.
You are right that each person can only know a finite network, therefore an upper bound must exist. IMO, the population of Earth is below that limit, at least when coupled with decent search tools.
What's really the difference between being able to phone a million people compared to a billion people?
Not the best choice of example, IMO. For the phone network, a million people doesn't even cover my local-distance landline region, which might be enough to order pizza but useless if I travel much. A billion people, OTOH, covers most if not all of the phones in the world.
The value of a network (telcom, social, or otherwise) is not just the connections that you directly use, but the ones that you know you COULD use if it were necessary.
No, not the OS. I'm saying the internet app itself (in this case, Sun JRE) should have a "newbie mode" where the users can't hose themselves just by clicking OK.
99% of users understand that by inserting a CD and running its contents, they are allowing that CD to control their computer. Maybe 50% (if we're lucky) realize the same is true of web browsers. For remote content, the default paradigm should be a padded room instead of a sandbox.
No, I would still call this a failing of the JRE and its interface. Any network-aware program designed to read/write arbitrary directories (as opposed to just temp/cache and user-initiated saves) also needs the ability to be locked down and protect non-technical users from their own ignorance.
The JRE should have an option where web applets CANNOT leave the sandbox, with no user-susceptible dialog. I would go further and say that this should be the DEFAULT setting for non-developer installs. Raise the bar of responsibility, and require the user to manually change the pref before they can endanger themselves.
After that, if they screw up then it's fair to say PEBKAC.
I think the Public Domain Expansion Act is almost what you're looking for. It doesn't go quite as far as your suggestion, but it's easier to implement and more likely to become law (odds 10e-6 instead of 10e-100).
Slashdot Mirror
And those users should be allowed to re-enable it. But it still should be blocked by default. And it definitely doesn't excuse Telewest for failing to cut off zombie hosts after receiving spam reports.
If an ISP does not block outbound 25 by default, and some of their customers are spam zombies, and they are notified about the offending PCs, and they don't stop the zombies, then that ISP is most definitely NOT the victim. Telewest is grossly negligent, therefore spam-supporting.
Preventing spam from your network is not just an afterthought or a courtesy, it is a RESPONSIBILITY. If you shirk it repeatedly, you should be held accountable.
telewest is not a spam support organisation
People receive spam that comes from Telewest IP space. Res Ipsa Loquitur.
If I worked fro an ISP, I'd simply care that many of my users are infected with trojans.
/18 BLOCKS LISTED IN SPEWS.
91degrees, please pay attention.
RTFA: TELEWEST DID *NOT* CARE UNTIL *AFTER* THEY GOT 56
That's the bottom line. They are cleaning up their act because their customers are complaining. Their customers are complaining because they are listed in SPEWS. They are listed in SPEWS because Telewest has been completely ignoring their spam zombie problem for a LONG time.
SPEWS WORKS. You may not like their methods, but they get results when other gentler attempts have failed.
As a long-time NANAer (heck, I supported its initial RFD/CFV) I can tell you that SPEWS has very simple rules, they follow those rules, and anyone who has argued with you about SPEWS is in fact NOT SPEWS.
Since those guys are not SPEWS, what the hell does your inflammatory tidbit have to do with anything?
- If you are the directly-listed ISP, you kick every single indicated spam source off your network, make the relevant DNS/Whois changes, and post these facts to NANA*. Assuming you are not a repeat offender, you should be removed within days or even hours.
- If you are a customer of the offending ISP, you either convince them to do #1 above, or leave them.
- There is no step 3. TINLC. TINS3.
p.s. I am SPEWSI would rather have Apple define "safe" properly and exclude anything capable of installing itself (or other files) outside of your designated download location.
Web page which drops a visible file on my desktop: not so bad.
Web page which adds anything to my Library folder: bad.
Just use our code
ASOT, I'm glad you're here, but you know damn well that APSL is incompatible with GPL, so Apple's launchd code CANNOT be used in Linux.
...and my PowerBook feels snappier already!
Yeah, government-created infrastructure is always a catastrophe. Like the national highway system, and municipal sewers, and 99% of the early internet, and ... oh wait, those actually work pretty damn well.
... look at how much better privately-run infrastructure works! For example, Comcast cable rarely goes down, customer service is prompt, and the costs are reasonable ... no wait, those are all false.
But But But
I don't have municipal internet in my residential area. I don't need or want it, and there are no plans to install it. But if the citizens of some other town think it's a good idea, why the hell should there be a law that forbids them from trying?
Those two all-beef patties you mentioned are explained in detail by Hannibal at Ars Technica.
MAPS stopped being a reputable service ever since they joined MFN/Abovenet. I say this as someone who previously supported MAPS and even donated to their legal defense fund.
It was quite sad to see them fall to the dark side. It's even sadder to see that MAPS is still in active use by anyone outside of MFN.
The US publishing lobbyists would say YES absolutely. In fact, they've been actively fighting against libraries (not to mention used book sellers) for several years. To them, the library system is just as "evil" as Kazaa.
The Lion King, like all standard animations, uses large swaths of relatively flat color punctuated by dark linework. Optimal compression for line art is substantially different from that of highly-shaded photographic imagery. Given that the vast majority of video available on TV is real-world, that test case seems like a poor indicator for typical performance.
I don't understand how a DNS or network capacity problem could cause a web server to respond with an explicit "404
If you use MSIE with the default "friendly error messages", then pretty much ANY failure (code 404, no DNS, congestion timeout, etc) displays the same generic error (which is also the same as the default 404 page sent by IIS).
Which is why when I'm trying to diagnose a customer's complaint about our web site "not working", the first thing I do is have them turn off "friendly" error messages (followed by some casual buzz for Firefox).
You mean like the Google SpamReport page? It exists.
They used to link to it at the bottom of some (random?) search result pages, but I haven't seen it posted publically in a while. Perhaps it didn't actually work as well as you or they hope it would.
modern P2P is more like the broadsword
The problem is that "P2P" is not monolithic, and each variation requires a different analogy. Things like Grokster were certainly intended to aid (illicit) media swapping, and their associated business entities don't help to dissuade this notion. OTOH we have stuff like BitTorrent, which has literally enourmous non-infringing uses (result #3 and similar notwithstanding).
Hmm...I'm having trouble here, what kind of blade is BitTorrent? Maybe a chainsaw powered by a beowulf cluster of tandem exercise bikes?
NOT in the same league as Einstein or Linus Torvalds
Funny that your parochial flamebait happens to be true. Ramanujan was definitively smarter than either of them.
Not to put down Big Al, but he only had a small armful of memorable discoveries spread over the decades of his career. OTOH, Ramanujan pumped out astonishingly brilliant stuff pretty much every day of his sadly brief adult life.
...is that IT'S ALREADY A WORD.
Plog is short for "plastic clog" (as in shoe). You'll see them quite often in hospitals because they're comfortable for standing and very easy to disinfect.
People have a right to be annoying in their own home, or office, or even in many public spaces. But when someone intrudes into my personal space (physical, email, phone, or otherwise) to be annoying, they better be prepared for a LARTing mallet.
if there were an infinite number of phone users
I think the important distinction is that the second component of the value equation (believed to be O(n), log(n), or otherwise) is dependent not on the total size of the network, but on the size of the sub-network that each user KNOWS HOW TO ACCESS. This is affected not just by size, but by usability, metadata, etc.
You are right that each person can only know a finite network, therefore an upper bound must exist. IMO, the population of Earth is below that limit, at least when coupled with decent search tools.
What's really the difference between being able to phone a million people compared to a billion people?
Not the best choice of example, IMO. For the phone network, a million people doesn't even cover my local-distance landline region, which might be enough to order pizza but useless if I travel much. A billion people, OTOH, covers most if not all of the phones in the world.
The value of a network (telcom, social, or otherwise) is not just the connections that you directly use, but the ones that you know you COULD use if it were necessary.
No, not the OS. I'm saying the internet app itself (in this case, Sun JRE) should have a "newbie mode" where the users can't hose themselves just by clicking OK.
99% of users understand that by inserting a CD and running its contents, they are allowing that CD to control their computer. Maybe 50% (if we're lucky) realize the same is true of web browsers. For remote content, the default paradigm should be a padded room instead of a sandbox.
No, I would still call this a failing of the JRE and its interface. Any network-aware program designed to read/write arbitrary directories (as opposed to just temp/cache and user-initiated saves) also needs the ability to be locked down and protect non-technical users from their own ignorance.
The JRE should have an option where web applets CANNOT leave the sandbox, with no user-susceptible dialog. I would go further and say that this should be the DEFAULT setting for non-developer installs. Raise the bar of responsibility, and require the user to manually change the pref before they can endanger themselves.
After that, if they screw up then it's fair to say PEBKAC.
I think the Public Domain Expansion Act is almost what you're looking for. It doesn't go quite as far as your suggestion, but it's easier to implement and more likely to become law (odds 10e-6 instead of 10e-100).