1) PERL is wonderful for admin scripts, and not too great for systems that have to parse large chunks of mail. It's just not fast enough in an enterprise environment.
2) DCC doesn't recognize MIME parts or do fuzzy checksumming. The lack of both makes it trivial to make spam/viruses that get around it.
SpamAssassin wasn't an option for my ISP because of these issues, so I wrote MessageWall to do most of SpamAssassin's work with enterprise-level speed.
"The purpose of the search warrant was to determine the identity of the person who sent the email that caused our system to fail so we could then determine whether further investigation would be necessary."
The search warrant cited our domain no less than 7 times. Had the detective taken the time to read the website, the situation would have been quite clear to him.
Second, this all could have been avoided if Ian Gulliver hadn't freaked when he got the order. If he'd waited a bleeding 24 hours this would have been resolved and ORBZ could have gone on its merry way.
Having more knowledge here of what went on than you, please trust me. In my opinion, this 'settlement' wouldn't have been nearly as forthcoming if a certain Wired.com article didn't cause major embarassment. I believe that this 'settlement' is much more public relations damage control than an actual realization that a mistake was made.
Re:There's something here we're not seeing
on
ORBZ Shuts Down
·
· Score: 5, Informative
I'm not going to comment on the current legal status. However, I will comment on the shutdown.
This shutdown isn't so much for this time, but for next time. I'm stuck fighting this one, but I don't have the time or inclination in my life to fight stupid pointless criminal charges on a weekly basis. Unfortunately, the way this world works, this'll be the tip of the iceberg once people realize that they can. Therefore, I'm out of this game.
If anyone is made uncomfortable with these terms and would like free webspace, CVS, FTP, etc. for their open source/free software project, just drop me an email. Always happy to help out.
MySQL has two table types that support row-level locking and transactions. One is tied up in this contractual mess, but the other, InnoDB has no such issues, and may even be faster for many purposes.
Please note that this (horribly overused) style of analogy is blatantly wrong; the reason that copyright infringement is not theft is that, unlike the car, the original owner does not lose their ability to use their property. A new user simply gains that ability. Things that have this property, such as anything that can be represented in a bitstream, should not be able to be owned. To try to enforce the laws of physical theft on such items is silly and is destined to fail.
For those of you who don't know what 10-digit dialing is (the article isn't very clear), he's an explanation from a phone company employee:
Users have to dial all 10 digits of a phone number whether its inside their area code or not; all phone numbers in the US are 10 digits. This frees up leading numbers such as 0 and 1 for creation of new exchanges and area codes. Please note that adding 0 and 1 to the set of 2-8 increases the size by 25%: thats not too much at the rate that number use is growing in the US. However, any move to 11 or 12 digit phone numbers should be dialing the entire number, so this is a step in the right direction.
Slashdot Mirror
1) PERL is wonderful for admin scripts, and not too great for systems that have to parse large chunks of mail. It's just not fast enough in an enterprise environment.
2) DCC doesn't recognize MIME parts or do fuzzy checksumming. The lack of both makes it trivial to make spam/viruses that get around it.
SpamAssassin wasn't an option for my ISP because of these issues, so I wrote MessageWall to do most of SpamAssassin's work with enterprise-level speed.
Having more knowledge here of what went on than you, please trust me. In my opinion, this 'settlement' wouldn't have been nearly as forthcoming if a certain Wired.com article didn't cause major embarassment. I believe that this 'settlement' is much more public relations damage control than an actual realization that a mistake was made.
I'm not going to comment on the current legal status. However, I will comment on the shutdown.
This shutdown isn't so much for this time, but for next time. I'm stuck fighting this one, but I don't have the time or inclination in my life to fight stupid pointless criminal charges on a weekly basis. Unfortunately, the way this world works, this'll be the tip of the iceberg once people realize that they can. Therefore, I'm out of this game.
If anyone is made uncomfortable with these terms and would like free webspace, CVS, FTP, etc. for their open source/free software project, just drop me an email. Always happy to help out.
MySQL has two table types that support row-level locking and transactions. One is tied up in this contractual mess, but the other, InnoDB has no such issues, and may even be faster for many purposes.
Please note that this (horribly overused) style of analogy is blatantly wrong; the reason that copyright infringement is not theft is that, unlike the car, the original owner does not lose their ability to use their property. A new user simply gains that ability. Things that have this property, such as anything that can be represented in a bitstream, should not be able to be owned. To try to enforce the laws of physical theft on such items is silly and is destined to fail.
For those of you who don't know what 10-digit dialing is (the article isn't very clear), he's an explanation from a phone company employee:
Users have to dial all 10 digits of a phone number whether its inside their area code or not; all phone numbers in the US are 10 digits. This frees up leading numbers such as 0 and 1 for creation of new exchanges and area codes. Please note that adding 0 and 1 to the set of 2-8 increases the size by 25%: thats not too much at the rate that number use is growing in the US. However, any move to 11 or 12 digit phone numbers should be dialing the entire number, so this is a step in the right direction.
Happy to host it aswell - drop me a line at ian@penguinhosting.net.