You are comparing fundamental technology with a huge complex beast that has a million do-dads and miles of wire and hurtles through the sky at thousands of miles per hour.
You might as well say "well planes still use bernoulli's principles to fly"
Anyway, you did admit your analogy was flawed.:)
Regarding the actual advances, the main ones would be in materials science and in computing. High strength lightweight composite materials are revolutionizing industries left and right.
The advances in computing are obvious, and I'm not saying to stick an Athlon in there either. Even the tough, highly reliable systems have advanced.
You do realize the shuttle was designed with core memory, right? Like hand-woven magnetic cores, for fuck's sake.
Just to nitpick, things don't burst into flame without ignition sources. Even in 100% oxygen under 2200psi of pressure. You don't see many oxygen tanks exploding on their own, do you?
The tiniest spark near anything remotely flammable would cause such a system to explode violently though.
Maybe because 500ppm at the sensor means 100% O2 near the area of the leak. Makes sense after all. If something started burning somewhere between the 100% part and the 500ppm part, it could spread very quickly in the direction of the leak. Once the tank gets hot, the leak would speed up which would feed the fire even more. You see where this is going end up.
The Dow is heavily overweight on the couple stocks with huge market caps though. Because it's only 30 stocks and is weighted by market cap, a company in the process of going under like MSFT will bring the whole Dow down significantly.
Yes, after submitting in hindsight I did recall that mercury vapors from boiling mercury are pretty toxic, I just generally think of the liquid form when talking about elemental mercury.
Also it wasn't elemental mercury, which is basically inert to humans.
One time at the high school I went to, a kid blew into a manometer and shot elemental mercury all over, they actually called hazmat and evacuated the building while they cleaned it up.
Hehe, kinda amusing, but drinking 200-400 sodas would take so long that the half-life of caffeine in your blood would be surpassed.
In other words, you'd be in a race with your liver, and your liver would probably win as you get sick of forcing down yet another cola after doing it for 24 hours straight and only knocking out 50-100.
In that link you cited the reciever only is injecting noise, in this system both sides are generating a stream of random bits.
It does have similarity in that it combines the knowledge of what random choices the reciever made along with the resulting line condition, but the end result is the construction of a OTP that is mirrored on both ends. (Literally mirrored, both ends will have an inverse copy of each other, all the bits will be NOT'ed).
It's important to note that the actual payload data is not sent during the initial bout of random bit flipping, but rather the data is conveyed by saying which of the secure (state unknowable to the eavesdropper) bits made up the message and in what order. This data can be sent clear in a public channel. This is where it is very much like a OTP, since it is unbreakable from a brute force standpoint.
There are optical routers using MEMS mirrors. In theory you could have a circuit switched network using QC based on this. I know the Internet isn't circuit switched, but still.
Say each side has a free running RNG producing 1 bit per clock. So either side might be 0 or 1 on any given clock.
The properties of Kirchoff's laws make for an easy way for the transmission bus to sum the endpoint values, such that only the sum is shown to an eavesdropper.
So the bus can have 3 values, 0, 1 or 2. If it's 0 or 2 it's easy to tell what state the endpoints are in, but if it's 1, the endpoints are at opposite states.
That's the crux of this, when the bus state is "1", each endpoint can note what their state is, and construct a type of one time pad from these "secure bits". The OTP will be a mirror image at each endpoint, since their states were opposite when they constructed it.
Once the OTP is large enough, the actual payload is transmitted over a public channel using the OTP.
So that's basically the theory of it. The way I understand it the noise only comes into play to obscure the potential differences in the endpoints that non-ideal components cause.
The best cryptographic and digital security is one that is very public, that has had many hundreds of people pounding on it for years trying to find flaws.
A secret system is likely to be broken as soon as someone more skillful than the designers learns of its existance.
This sounds very good in theory, but it may be difficult to implement securely.
For example, he claims an eavesdropper could inject current to measure voltage drops, but would be discovered on the first attempt. If the eavesdropped can send a pulse of current that is so small as to not be registered on the endpoint equipment (which say samples the line at 1X sampling rate), but the attacker is injecting and sampling at a rate 100X faster, the attacker's pulse will be so far above the nyquist bandwidth of the endpoints that they will never see it.
I admit I only read the abstract, he may address this later on in the paper.
Linux isn't all that bug free, many very widely used drivers have serious bugs in 2.6 still.
The big advantage of it being open source is that you can write the developers or a developers mailing list and they can tell you what they know about the bug.
Ever try that with commercial software? You find a bug, and then spend a few weeks trying to convince them it is indeed not a misconfiguration or user error. Then they often come up with some outrageous workaround that takes 3 times longer to do, and then declare that since there's a workaround it's not a bug. Good luck trying to reach an actual programmer at the company. If they do acknoledge it's a bug, you'll have to wait 6 months for it to be fixed, compared with open source where you can often get a patch in less than a week, if it's a trivial fix.
Not all open source software is this way, and you can run into the above scenario with certain open source software *cough*mozillaproject*cough*, but it's a lot less common.
Slashdot Mirror
You are comparing fundamental technology with a huge complex beast that has a million do-dads and miles of wire and hurtles through the sky at thousands of miles per hour.
:)
You might as well say "well planes still use bernoulli's principles to fly"
Anyway, you did admit your analogy was flawed.
Regarding the actual advances, the main ones would be in materials science and in computing. High strength lightweight composite materials are revolutionizing industries left and right.
The advances in computing are obvious, and I'm not saying to stick an Athlon in there either. Even the tough, highly reliable systems have advanced.
You do realize the shuttle was designed with core memory, right? Like hand-woven magnetic cores, for fuck's sake.
I see. So as long as we good a good value for every american life lost, then it's morally OK.
I'm opposed to both based on the fact that both are unnecessary taxation and unconstitutional, but that's a different ball of wax.
Just to nitpick, things don't burst into flame without ignition sources. Even in 100% oxygen under 2200psi of pressure. You don't see many oxygen tanks exploding on their own, do you?
The tiniest spark near anything remotely flammable would cause such a system to explode violently though.
We have many (MANY) technological advancements because of war too. I don't see people advocating your point of view generally advocating that though.
I'm no Hawk, just a Libertarian pointing out some hypocrisy.
Yes, but still using the shuttle in 2005 is akin to using canvas winged biplanes for general public transportation in 1960.
Technology has advanced a ton in the last 35 years. It's incredibly stupid to use these obselete machines in anything but a museum.
Taking a stab in the dark:
Maybe because 500ppm at the sensor means 100% O2 near the area of the leak. Makes sense after all. If something started burning somewhere between the 100% part and the 500ppm part, it could spread very quickly in the direction of the leak. Once the tank gets hot, the leak would speed up which would feed the fire even more. You see where this is going end up.
Even if allofmp3 isn't paying all the licenses they should (even though there's strong evidence they are), that's not the consumer's problem.
That's like saying the consumer is liable if their car manufacturer loses a patent infringement suit. It just doesn't work that way.
Gah, you are right!
I must have been thinking of the S&P 500.
AllofMp3 is legal, not "quasi-legal".
The Dow is heavily overweight on the couple stocks with huge market caps though. Because it's only 30 stocks and is weighted by market cap, a company in the process of going under like MSFT will bring the whole Dow down significantly.
Yes, after submitting in hindsight I did recall that mercury vapors from boiling mercury are pretty toxic, I just generally think of the liquid form when talking about elemental mercury.
Hmm..
I guess we should thank the people writing and using IE exploits, they will ensure no one uses an obselete IE browser in the coming years.
Also it wasn't elemental mercury, which is basically inert to humans.
One time at the high school I went to, a kid blew into a manometer and shot elemental mercury all over, they actually called hazmat and evacuated the building while they cleaned it up.
Such a waste caused by ignorance.
Hehe, kinda amusing, but drinking 200-400 sodas would take so long that the half-life of caffeine in your blood would be surpassed.
In other words, you'd be in a race with your liver, and your liver would probably win as you get sick of forcing down yet another cola after doing it for 24 hours straight and only knocking out 50-100.
In that link you cited the reciever only is injecting noise, in this system both sides are generating a stream of random bits.
It does have similarity in that it combines the knowledge of what random choices the reciever made along with the resulting line condition, but the end result is the construction of a OTP that is mirrored on both ends. (Literally mirrored, both ends will have an inverse copy of each other, all the bits will be NOT'ed).
It's important to note that the actual payload data is not sent during the initial bout of random bit flipping, but rather the data is conveyed by saying which of the secure (state unknowable to the eavesdropper) bits made up the message and in what order. This data can be sent clear in a public channel. This is where it is very much like a OTP, since it is unbreakable from a brute force standpoint.
There are optical routers using MEMS mirrors. In theory you could have a circuit switched network using QC based on this. I know the Internet isn't circuit switched, but still.
Yeah he just sorta waves his hands and says that a fast, high current, pulse would be detected without elaborating.
The way I understand it is more like this.
Say each side has a free running RNG producing 1 bit per clock. So either side might be 0 or 1 on any given clock.
The properties of Kirchoff's laws make for an easy way for the transmission bus to sum the endpoint values, such that only the sum is shown to an eavesdropper.
So the bus can have 3 values, 0, 1 or 2. If it's 0 or 2 it's easy to tell what state the endpoints are in, but if it's 1, the endpoints are at opposite states.
That's the crux of this, when the bus state is "1", each endpoint can note what their state is, and construct a type of one time pad from these "secure bits". The OTP will be a mirror image at each endpoint, since their states were opposite when they constructed it.
Once the OTP is large enough, the actual payload is transmitted over a public channel using the OTP.
So that's basically the theory of it. The way I understand it the noise only comes into play to obscure the potential differences in the endpoints that non-ideal components cause.
Wow, that's so wrong. I wonder who modded you up.
The best cryptographic and digital security is one that is very public, that has had many hundreds of people pounding on it for years trying to find flaws.
A secret system is likely to be broken as soon as someone more skillful than the designers learns of its existance.
those who can afford to increase their muscle mass using the products would perhaps become a superior segment of the human race.
What the hell are you babbling about. I don't see the "Body Builder Party" coming into power in any country.
In this case you'd want to measure the voltage drop properties of the line to figure out what resistances were on either end.
This sounds very good in theory, but it may be difficult to implement securely.
For example, he claims an eavesdropper could inject current to measure voltage drops, but would be discovered on the first attempt. If the eavesdropped can send a pulse of current that is so small as to not be registered on the endpoint equipment (which say samples the line at 1X sampling rate), but the attacker is injecting and sampling at a rate 100X faster, the attacker's pulse will be so far above the nyquist bandwidth of the endpoints that they will never see it.
I admit I only read the abstract, he may address this later on in the paper.
Can you post a reference on the Libertarian Party problems you mention?
I've seen some things, but it looked to me to be more petty infighting than anything near what the other parties do to this country every day.
If we combined all the best parts of all the different Office software out there, it might be acceptable.
I had a longer message written, but i'm not going to rehash all that is wrong with the current Office packages, that's basically all it was.
Linux isn't all that bug free, many very widely used drivers have serious bugs in 2.6 still.
The big advantage of it being open source is that you can write the developers or a developers mailing list and they can tell you what they know about the bug.
Ever try that with commercial software? You find a bug, and then spend a few weeks trying to convince them it is indeed not a misconfiguration or user error. Then they often come up with some outrageous workaround that takes 3 times longer to do, and then declare that since there's a workaround it's not a bug. Good luck trying to reach an actual programmer at the company. If they do acknoledge it's a bug, you'll have to wait 6 months for it to be fixed, compared with open source where you can often get a patch in less than a week, if it's a trivial fix.
Not all open source software is this way, and you can run into the above scenario with certain open source software *cough*mozillaproject*cough*, but it's a lot less common.