Anybody local to The Dalles has known about this for quite a while now. Google bought the entire land area of the old port and started moving employees up from California. I've known about this project for many months but was told to stay quiet about it. This is the first I've heard of the purpose of the new facility, though.
It's amazing that such a huge development went unnoticed in the media, although Google didn't take any particular pains to keep it secret other than telling the employees involved to keep theirs mouths shut. Now that the story's finally broke, I can say "Yippee!" I'm not so much excited that it's Google, per se, just that such an enormous and successful tech company is moving into the Gorge.
I've been told by a guy at Google, only half-jokingly, that I could probably make a good business microbrewing beer for the Google employees in The Dalles.
Actually, the real problem is that they included the original spaces in the ciphertext. This is basically unencrypted information leaking through. This allowed the analyst to locate the encrypted form of the word "Louisville." It was this one big break that revealed the entire key.
Had the cipher makers not included spaces, and just packed all the words directly together, this attack would not have been so easy. There are other methods for determining the key of a Vigenere cipher, but they are difficult to use on such short messages.
Commercial Software - 100 to 1000 dollars each - something more substantial as a penalty
"Substantial?" Hardly. Even if the software maker was paying out a $1000 fine once a week, that only comes to $52,000 per year. If it costs them $75,000 per year to hire someone competent enough to keep their software working reliably, guess what course of action they'll take?
"More than $10,000" for faulty software in the NATIONAL SECURITY arena? Are you freaking insane? Even $100,000 is less than a single executive makes in a year. A better penalty would be, say, a fine equal to triple the cost the government paid for the software (which is likely to be many millions of dollars).
I do think software makers should be liable for bugs, but only through agreement/contract with the user. If the liability isn't agreed upon, then there is none. If it IS agreed upon, the software maker can purchase liability insurance, the end user can receive a payout if something fucks up, and everybody stays happy.
Had she actually drank the coffee rather than spilled it, she'd have had permanent scarring on her esophagus and tongue and probably would have lost the ability to speak.
Bullshit. You have multiple reflexes to prevent you from ingesting boiling or near-boiling materials. 180-degree coffee would hardly get past the lips, much less down the throat.
When you put your hand in a fire, do you CONSCIOUSLY pull it away or is it an automatic reflex? On the contrary, it requires severe conscious control to KEEP the hand near the heat even if you wanted to.
I didn't exactly receive any thanks, either, though. Back in the early 90's I had a shell account on a local UNIX system. The system was set up to let people automatically create new accounts, which were then authorized by the administrators. To do this, you logged in as the user called "new."
Well, first thing that happens when you did that, was you read their terms of service in a "more" listing. Of course, it was easy to hit Ctrl-Z and drop to a shell at that point. Once in the shell, I did an "ls" of the "new" user's home directory. Lo and behold, in that directory was a file containing all the new users created that day, along with their system-assigned passwords.
Funny thing -- most users never change their passwords. I had the master list to almost 90% of the accounts on the system! It got better, though. I noticed certains patterns in the assigned passwords. E.g., the last three chars of one password where the same as the first three of some other password. I wrote a program to piece it all together.
Turns out, the "random" passwords were drawn from a 512-character string, with the beginning point randomly selected. So I busted the string up into each possible password and ran the thing through a crack program. Now I had closer to 99% of the accounts on the system!
I reported this, and suggested that perhaps the system-assigned password algorithm was weak. The admins grumbled and yelled but didn't threaten any legal actions.
I pissed them off again later, with an accidental fork bomb. I lost my account that time:-)
Better not walk on a white sand beach then, it's practically the same thing.
I don't understand. Are you denying that this person has glass in his foot? The doctors seemed to think so. Yet a white sand beach does not slice your feet. I think it's pretty obvious that they are not "practically the same thing." Hint: look at a grain of sand under a microscope. Doesn't look very sharp, does it?
Keeping Hydrogen gas inside metal gas containers is no problem, by the way. You can buy and store it, just like other gases (for regular materials the size difference of He- and H2-molecules really don't matter).
You apparently haven't heard of hydrogen embrittlement. Hydrogen can diffuse into the lattice of metals and weaken them. In the case of carbon steel, the H2 combines with carbon to produce microscopic pockets of methane! Storing hydrogen is tricky business. I'm not saying it can't be done, but you can't just blow H2 into a tank designed for N2 (for instance) and hope everything will be okay over time.
as long as they trust the editor to catch their mistakes, they'll never actually learn to avoid them; they'll simply let the IDE be their guide and never learn it.
What the hell? How about this: as long as they trust the compiler to catch their mistakes, they'll never actually learn to avoid them. How is the IDE reporting an out-of-scope variable any different than the COMPILER reporting the out-of-scope variable? Hey, even better idea: compilers shouldn't check syntax errors -- if the source code isn't kosher it should just silently generate a no-op object file. That way the students can learn how not to commit syntax errors without the "crutch" of having the compiler report them.
similarly, as long as they can debug in the IDE, they'll never learn real debugging techniques that the "cold metal", or even just debugging a running server they can't get an IDE into.
NO programming student I have EVER seen has used an IDE debugger. They are too fucking difficult to figure out. Every student I've seen uses printf() to debug. You're complaining about something that isn't even a problem -- this shows that you are disconnected from reality and the rest of your arguments can be safely ignored.
You've got another 41 years (in our frame of reference) until they get here, though, assuming they can travel nearly light speed. As they get closer they will hear a very blue-shifted version of all the radio transmissions from that time up until now, so maybe they'll change their minds en route.
On the other hand, if they are travelling near light speed, in THEIR frame only a few seconds or minutes will have passed, so maybe they won't be able to comprehend the new transmissions in time and blow us away anyway (assuming the most recent 41 years worth of data is enough to vindicate us in the first place).
In the reference frame of the spacecraft, you'd save a few years due to special relativity. I calculated it, it's on the order of tens of years, but I won't post the exact number since all these other numbers are guesses anyway (except of course the speed of light).
After a certain pixel count, there's not much point in going much further in consumer devices. You're just adding data, but not improving the viewable image. Why have an image that is higher res than a monitor or your eyeball's ability to process data? Where is that cut-off?
Uh, some of us like to PRINT our images. Being able to make large prints is a hugely good thing. Not to mention being able to ZOOM IN on small parts of an image and still see detail.
It staggers me that no other use occurs to you for a digital photo than on-screen viewing. Hello?
Changing the size of the fundamental units merely changes the value of the various physical constants. Physics works just fine no matter what units you use. However, a redefinition of the physical constants would open the possibility of accidentally mixing old and new units in a calculation (and NASA has shown us what sorts of things can happen in that event).
Would not two photons/beams of light travelling in opposite directions be moving faster than the speed of light *relative* to one another?
If you were somehow able to OBSERVE the two photons (which you can't, but just imagine), you would see the distance between them seperating at twice the speed of light. But there is no OBJECT anywhere (i.e., either one of the photons) which can be observed to travel faster than light.
It's like the concept of a moving shadow. A shadow can "move" much faster than light across a surface, but a shadow is not actually an object.
Now, your question asked "are they traveling faster than light relative to each other?" The reference frame of a photon is a very tricky thing. Time vanishes in that frame, and the question of the speed of two photons relative to each other is meaningless.
No, it isn't. If you place a phone next to a CRT and dial it, you'll see the CRT begin wavering before the phone even displays the caller information or starts ringing. There is some sort of burst at a particular frequency that occurs as a call is being connected (it goes away once you're actually having a conversation, so it clearly isn't the magnet in the speaker).
Besides, the speaker magnet is a puny little thing.
Except that the format I want is basically the default format but with the year included. THAT option doesn't seem to be present in the list. The fifth one down is kind of close, but abbreviates the day, month and year.
Re:Mispronunciation
on
SQL Cookbook
·
· Score: 1, Informative
SQL started out being called SEQUEL (and pronounced as such) until it was changed to SQL due to trademark issues. IMHO, the historical pronunciation is a valid precedent. See the History section of the SQL Wikipedia entry.
From the POPClock, there are currently 298,000,000 Americans in the world, and 6.5 billion people total. So Americans make up about 4.5% percent of the people on earth. There were 4 Americans in the final 48 contestants, that's about 8.3% for those of you who can't divide.
So Americans are overperforming their expected representation in the set of winners by 84%. How is that a scarce showing? You have to be arrogant and ignorant to expect much better than that.
Did you accidentally reply to somebody else's comment in the wrong thread? I'm utterly baffled at how my comment in any way implied the things you seem to think it implied.
Did I not say: "Just get out of the damn chair every once in a while?" I was merely expressing shock that this person sat still in a chair for an *8 hour period*. Somehow you've inferred from this that I am a brown-nosing chair dweller? Seriously, what drugs are you taking?
Another big-business-protecting law masquerading as protecting "the People", no doubt. Similar to various states' laws against microbreweries in bars.
The law was passed before I was born, but from what I understand it was ostensibly to help provide jobs during the oil crisis in the 70's, as well as because of "safety issues." I don't think that was the real motivation but honestly I can't figure out what the true one is.
Oddly, Oregon is one of the most liberal states with regard to beer and brewing (I say oddly because despite the tyrannical practices of the OLCC, microbrew is considered one of our regional tourist draws and is therefore heavily encouraged). There's practically a brewpub every other city block here. I brew my own myself.
Despite the fact that my post has inexplicably been modded Informative (when pretty much everything I said was phrased as a question), I was not trying to inform anybody of anything in particular. From your post it sounds like you've suffered DVT even though you thought you were doing things right. THAT'S informative.
Slashdot Mirror
Anybody local to The Dalles has known about this for quite a while now. Google bought the entire land area of the old port and started moving employees up from California. I've known about this project for many months but was told to stay quiet about it. This is the first I've heard of the purpose of the new facility, though.
It's amazing that such a huge development went unnoticed in the media, although Google didn't take any particular pains to keep it secret other than telling the employees involved to keep theirs mouths shut. Now that the story's finally broke, I can say "Yippee!" I'm not so much excited that it's Google, per se, just that such an enormous and successful tech company is moving into the Gorge.
I've been told by a guy at Google, only half-jokingly, that I could probably make a good business microbrewing beer for the Google employees in The Dalles.
Actually, the real problem is that they included the original spaces in the ciphertext. This is basically unencrypted information leaking through. This allowed the analyst to locate the encrypted form of the word "Louisville." It was this one big break that revealed the entire key.
Had the cipher makers not included spaces, and just packed all the words directly together, this attack would not have been so easy. There are other methods for determining the key of a Vigenere cipher, but they are difficult to use on such short messages.
"Substantial?" Hardly. Even if the software maker was paying out a $1000 fine once a week, that only comes to $52,000 per year. If it costs them $75,000 per year to hire someone competent enough to keep their software working reliably, guess what course of action they'll take?
"More than $10,000" for faulty software in the NATIONAL SECURITY arena? Are you freaking insane? Even $100,000 is less than a single executive makes in a year. A better penalty would be, say, a fine equal to triple the cost the government paid for the software (which is likely to be many millions of dollars).
I do think software makers should be liable for bugs, but only through agreement/contract with the user. If the liability isn't agreed upon, then there is none. If it IS agreed upon, the software maker can purchase liability insurance, the end user can receive a payout if something fucks up, and everybody stays happy.
Bullshit. You have multiple reflexes to prevent you from ingesting boiling or near-boiling materials. 180-degree coffee would hardly get past the lips, much less down the throat.
When you put your hand in a fire, do you CONSCIOUSLY pull it away or is it an automatic reflex? On the contrary, it requires severe conscious control to KEEP the hand near the heat even if you wanted to.
Well, first thing that happens when you did that, was you read their terms of service in a "more" listing. Of course, it was easy to hit Ctrl-Z and drop to a shell at that point. Once in the shell, I did an "ls" of the "new" user's home directory. Lo and behold, in that directory was a file containing all the new users created that day, along with their system-assigned passwords.
Funny thing -- most users never change their passwords. I had the master list to almost 90% of the accounts on the system! It got better, though. I noticed certains patterns in the assigned passwords. E.g., the last three chars of one password where the same as the first three of some other password. I wrote a program to piece it all together.
Turns out, the "random" passwords were drawn from a 512-character string, with the beginning point randomly selected. So I busted the string up into each possible password and ran the thing through a crack program. Now I had closer to 99% of the accounts on the system!
I reported this, and suggested that perhaps the system-assigned password algorithm was weak. The admins grumbled and yelled but didn't threaten any legal actions.
I pissed them off again later, with an accidental fork bomb. I lost my account that time :-)
This forgets the third option, which is to keep your mouth shut.
I don't understand. Are you denying that this person has glass in his foot? The doctors seemed to think so. Yet a white sand beach does not slice your feet. I think it's pretty obvious that they are not "practically the same thing." Hint: look at a grain of sand under a microscope. Doesn't look very sharp, does it?
You apparently haven't heard of hydrogen embrittlement. Hydrogen can diffuse into the lattice of metals and weaken them. In the case of carbon steel, the H2 combines with carbon to produce microscopic pockets of methane! Storing hydrogen is tricky business. I'm not saying it can't be done, but you can't just blow H2 into a tank designed for N2 (for instance) and hope everything will be okay over time.
What keeps a grain of sand from breaking?
What the hell? How about this: as long as they trust the compiler to catch their mistakes, they'll never actually learn to avoid them. How is the IDE reporting an out-of-scope variable any different than the COMPILER reporting the out-of-scope variable? Hey, even better idea: compilers shouldn't check syntax errors -- if the source code isn't kosher it should just silently generate a no-op object file. That way the students can learn how not to commit syntax errors without the "crutch" of having the compiler report them.
similarly, as long as they can debug in the IDE, they'll never learn real debugging techniques that the "cold metal", or even just debugging a running server they can't get an IDE into.
NO programming student I have EVER seen has used an IDE debugger. They are too fucking difficult to figure out. Every student I've seen uses printf() to debug. You're complaining about something that isn't even a problem -- this shows that you are disconnected from reality and the rest of your arguments can be safely ignored.
The learning curve has a top? As in, once you hit that point you start to get DUMBER? I had no idea.
On the other hand, if they are travelling near light speed, in THEIR frame only a few seconds or minutes will have passed, so maybe they won't be able to comprehend the new transmissions in time and blow us away anyway (assuming the most recent 41 years worth of data is enough to vindicate us in the first place).
Interstellar travel is weird like that.
In the reference frame of the spacecraft, you'd save a few years due to special relativity. I calculated it, it's on the order of tens of years, but I won't post the exact number since all these other numbers are guesses anyway (except of course the speed of light).
Uh, some of us like to PRINT our images. Being able to make large prints is a hugely good thing. Not to mention being able to ZOOM IN on small parts of an image and still see detail.
It staggers me that no other use occurs to you for a digital photo than on-screen viewing. Hello?
Changing the size of the fundamental units merely changes the value of the various physical constants. Physics works just fine no matter what units you use. However, a redefinition of the physical constants would open the possibility of accidentally mixing old and new units in a calculation (and NASA has shown us what sorts of things can happen in that event).
If you were somehow able to OBSERVE the two photons (which you can't, but just imagine), you would see the distance between them seperating at twice the speed of light. But there is no OBJECT anywhere (i.e., either one of the photons) which can be observed to travel faster than light.
It's like the concept of a moving shadow. A shadow can "move" much faster than light across a surface, but a shadow is not actually an object.
Now, your question asked "are they traveling faster than light relative to each other?" The reference frame of a photon is a very tricky thing. Time vanishes in that frame, and the question of the speed of two photons relative to each other is meaningless.
Besides, the speaker magnet is a puny little thing.
Congratulations -- that's the best joke I've seen on Slashdot in YEARS.
Ummm... Those who have common sense would have no need to search for it, would they?
Except that the format I want is basically the default format but with the year included. THAT option doesn't seem to be present in the list. The fifth one down is kind of close, but abbreviates the day, month and year.
SQL started out being called SEQUEL (and pronounced as such) until it was changed to SQL due to trademark issues. IMHO, the historical pronunciation is a valid precedent. See the History section of the SQL Wikipedia entry.
So Americans are overperforming their expected representation in the set of winners by 84%. How is that a scarce showing? You have to be arrogant and ignorant to expect much better than that.
Did I not say: "Just get out of the damn chair every once in a while?" I was merely expressing shock that this person sat still in a chair for an *8 hour period*. Somehow you've inferred from this that I am a brown-nosing chair dweller? Seriously, what drugs are you taking?
The law was passed before I was born, but from what I understand it was ostensibly to help provide jobs during the oil crisis in the 70's, as well as because of "safety issues." I don't think that was the real motivation but honestly I can't figure out what the true one is.
Oddly, Oregon is one of the most liberal states with regard to beer and brewing (I say oddly because despite the tyrannical practices of the OLCC, microbrew is considered one of our regional tourist draws and is therefore heavily encouraged). There's practically a brewpub every other city block here. I brew my own myself.
Despite the fact that my post has inexplicably been modded Informative (when pretty much everything I said was phrased as a question), I was not trying to inform anybody of anything in particular. From your post it sounds like you've suffered DVT even though you thought you were doing things right. THAT'S informative.