*IAA might not be able to sue the actual file sharers on Tor, but it looks like it might be vulnerable to the same attack that was use on Bit Torrent: go for the trusted nodes or the servers that maintain the lists of trusted nodes on grounds of contributory copyright infringement.
There will be a mighty "thpppppppt" as the blimp deflates and zooms around the sky, finally fluttering limply to the ground a suffocating some poor shmoe who just happened to be walking in the wrong place at the wrong time.
Speaking as someone that lives just outside of Woking (where the book is set), and who has walked his dog in the actual sandpit where the martians landed...
The Martians are going to be pissed when they step out of their cylinders and have to scrape their shoes off on the curb.
I, for one, would like to welcome our new poopey-shoed overlords.
This is/., and I know we hate the MPAA/Networks/RIAA/whatever, but a big part of what we dislike is the fact that what they create is invariably dumbed down for the lowest common denominator of viewers.
We need to support shows that hold the line on quality programming.
Also, from what I've seen on the web, JMS has also resisted the temptation to exploit B5 by merchandising crappy products. Instead he's allowed fans to produce products for fans.
One guy I worked with: "No, I'm not sure what the requirements of this program are, and I don't really know the programming language. I just code until it works."
IIRC: According to the doctor that was in B2, the weight loss was expected due to the diets that they were following (calorie restricted) and by and large, the crew was actually happy with the weight loss.
The reason that they had to open the doors and bring in supplies was that they didn't count on how fast the bugs would take over. The bugs started eating everything they could grow, and also were using up the oxygen.
I've thought about the same thing but I always run into the same problem: no matter what you write your library in, it will have to be able to interface to C/C++.
That means that, although your language may check every array bound before every access, and test every pointer for validity before each use, and place sentinals on the stack to detect overflows, you will still be accepting data from a program that may have miscalculated its array bounds or somesuch error.
You basically need to write libraries that assume the caller is hostile to the functioning of your library. That means structuring interfaces to them that may be less than optimal or convienient, which would in turn tend to discourage programmers from using your libraries.
I've coded plenty before and I've never encountered an instance where I can't check to see if a buffer overflow has occurred.
But do you always check? If you have, then you're an exceptional programmer, but you probably have very low productivity. Not that the latter is always a bad thing, because your code is completely bulletproof, but when a deadline looms you start coding for speed.
But even when I've taken drastic steps to bulletproof my code (testing every parameter, checking every return value, etc.), I still have made errors. Cut-and-paste errors happen all the time in production environments. Or you check your function parameters but forget about some specific case (causing an erroneous rejection). Or the infamous, and still all too common, off-by-one error.
Whoever they cast as Dejah Thoris had better look good. I believe that she went topless, or nude, in the books (it's been quite a while since I read them).
Just wait until Linux comes home with a new tattoo and a pierced tongue. Linus is going to hit the ceiling. (And he's probably going to want to know whose tongue it is.)
Slashdot Mirror
*IAA might not be able to sue the actual file sharers on Tor, but it looks like it might be vulnerable to the same attack that was use on Bit Torrent: go for the trusted nodes or the servers that maintain the lists of trusted nodes on grounds of contributory copyright infringement.
There will be a mighty "thpppppppt" as the blimp deflates and zooms around the sky, finally fluttering limply to the ground a suffocating some poor shmoe who just happened to be walking in the wrong place at the wrong time.
I, for one, would like to welcome our new poopey-shoed overlords.
I second Ziviyr's thought. (Buy the DVD's.)
/., and I know we hate the MPAA/Networks/RIAA/whatever, but a big part of what we dislike is the fact that what they create is invariably dumbed down for the lowest common denominator of viewers.
This is
We need to support shows that hold the line on quality programming.
Also, from what I've seen on the web, JMS has also resisted the temptation to exploit B5 by merchandising crappy products. Instead he's allowed fans to produce products for fans.
OK, you win.
Moderators: give this guy all your -1's
You slashdotted eviloverlord.com. Bastards!
I'm sure they will exact revenge for this... um... as soon as they sweep up the debris from their server.
I, for one, would like to welcome our robot cockroach overlords.
One guy I worked with: "No, I'm not sure what the requirements of this program are, and I don't really know the programming language. I just code until it works."
Forget that! My wives may be reading my email!
Cell phones with frikkin laser beams mounted on them.
They tried using sea bass, but there were too many dropped calls.
Maybe you have nothing to fear.
From to this article, we now know that the sharks may only be reading slashdot (or looking at shark pr0n).
Well, don't say that we didn't warn you.
IIRC:
According to the doctor that was in B2, the weight loss was expected due to the diets that they were following (calorie restricted) and by and large, the crew was actually happy with the weight loss.
The reason that they had to open the doors and bring in supplies was that they didn't count on how fast the bugs would take over. The bugs started eating everything they could grow, and also were using up the oxygen.
Here's the real thing.
It uses a new variant of TCP/IP connection called "aggressive negotiation".
I've thought about the same thing but I always run into the same problem: no matter what you write your library in, it will have to be able to interface to C/C++.
That means that, although your language may check every array bound before every access, and test every pointer for validity before each use, and place sentinals on the stack to detect overflows, you will still be accepting data from a program that may have miscalculated its array bounds or somesuch error.
You basically need to write libraries that assume the caller is hostile to the functioning of your library. That means structuring interfaces to them that may be less than optimal or convienient, which would in turn tend to discourage programmers from using your libraries.
But even when I've taken drastic steps to bulletproof my code (testing every parameter, checking every return value, etc.), I still have made errors. Cut-and-paste errors happen all the time in production environments. Or you check your function parameters but forget about some specific case (causing an erroneous rejection). Or the infamous, and still all too common, off-by-one error.
Now maybe we can figure out some new symbols that mean "play", "fast-forward", "rewind", etc.
Those triangles and double triangles are pretty meaningless once you're talking about anything other than tape.
Does it run Windows?
Barsoonian warriors challenged each other by grabbing their metals* and slapping the other in the face with them.
:)
Are you certain that "metals" wasn't a euphemism for something else?
And with that image implanted firmly in your mind, I leave you
Whoever they cast as Dejah Thoris had better look good. I believe that she went topless, or nude, in the books (it's been quite a while since I read them).
Of course, you could also jump into your time machine and visit the house of the future at Disneyland, circa 1957.
It was made so well that the wrecking ball just bounced off of it when they tried to demolish it. They had to bring in a crew with saws.
Nonsense! Now it is ready the the Klingon Age of Ascension!
Weapons are the proper gift for such a warrior as this!
Qapla'!
Just wait until Linux comes home with a new tattoo and a pierced tongue. Linus is going to hit the ceiling. (And he's probably going to want to know whose tongue it is.)