The only way that would have been cooler is if you had been able to work in Several Species of Small Furry Animals Gathered Together in a Cave and Grooving with a Pict.
Wait, 2-digit year format? If you're having problems with the transition from "09" to "10", then you'd also have problems with the transition from "2009" to "2010". A Y2K-like bug would mean that the INPUT value is incomplete, or essentially pre-truncated. What you describe is code that intentionally truncates the value itself. The client had better not get any blame for this.
No, it's not. The premise of my scenario was "you're looking for someone in a city", meaning that you already know the identity of the individual.
Looking at the general issue that my example was trying to address, the 'whole point' is that most of the information overwhelming intelligence agencies is probably entirely irrelevant.
1. Having information expire before it is discovered follows practical usage of encryption.
2. Basically, an extra layer is being applied at the content level: slang and the like are just word substitution.
3. Too much information probably indicates that attention is being diverted to cover unnecessary discussions. Think of it this way: you're looking for someone in a city. You could wiretap a few people close to that person and hope you catch some bit of conversation OR you wiretap the whole city guaranteeing you have every bit of conversation. The first approach will offer information in real time while the second approach will take years to discover relevant information. The first approach is adopted for speed, while the only reason to adopt the second is for archiving.
"Specifically designed for a stealth attack on the U.S. East Coast--perhaps targeting Washington, D.C., and New York City--the "samurai subs" were fast, far-ranging,..."
I have doubts about this - with the Panama canal under Allied control, getting to the east coast USA from Japan would have been VERY far-ranging.
Stealth bombers have one fundamental design problem - none have equally stealthy bomb bay doors, when open.
You get the stealth advantage going in, but now they see you and you better hope the non-stealthy parts are superior to the countermeasures of your opponent.
ZOMG!!!! A massive explosion!!! A six mile high explosion!!!! Or would that actually be a very, very modest explosion (especially in astronomical terms) triggering a six mile high debris plume?
Right, astronomical terms. On that scale, one could argue that Earth occupies an infinitesimally small volume so destroying it should be of only minor consequence as well.
How about we limit destructive tests to things that we have in multiple quantities?
There's a Democrat in the White House who's in the process of making his own blocks on this chart look like the freakin' Sears Tower in comparison to what's there now.
There's one 'glitch' listed for Oblivion that is not: slaughterfish gasping. A fish could spawn over land depending on the location of your load point - THAT issue should be the glitch. But if it does appear over land, what do you expect a fish to do?
A gasping fish is an intentional feature, not a bug or glitch.
Sometimes we are blessed with the opportunity to provide real world examples.
In the case of FaceBook, the user grants certain content usage rights to FaceBook (presumably to advertise FaceBook itself). In the linked example above, the user granted Creative Commons licensing to everyone. Technically different, but it seems similar enough to properly illustrate your point.
By the way, this seems to be a follow up on that example. The lesson: you give your privacy away, others will take it.
I haven't played Starcraft online for a nearly a decade, so they may have patched my favorite strategy: using the Zerg Queen to parasite all available animals.
Since those units are never highlighted as hostile, players usually ignore them - killing them only if their presence interfered with a potential building site.
Once set, you'd have a bunch of covert spies all over the map. Flying animals were prized due to their mobility and were even less likely to be killed by players.
Applying this issue to just one LED is overreaching its significance, but the other comment was talking about many LEDs - increasing the overall amount of available surface area. Although, from what you say, it would take an awful lot of them to cause arsenic poisoning.
Actually, from what I understand, it would take about six 125mm wafers of GaAs to reach the LD50 for arsenic poisoning, if completely disassociated. That's a lot of material, all by itself.
Of course, it's probably safe to assume that the original comment referred to encased LEDs. If someone is eating encased LEDs, they'd most likely only encounter problems from the actual shape of the container (the metal leads in particular) as it passes through them so all this talk about etching becomes insignificant anyway.
While I'm moderately familiar with the general manufacturing process and the possibility of this specific hazard, I haven't been exposed to much of the practical side of manufacturing so I wasn't aware of the actual etching time frame. Thanks for the info.
How about this: 1. Acids are routinely used for wet etching GaAs - the crystal disassociates the two elements when exposed to acid. 2. Your stomach contains such acid - meaning we now have free floating Gallium and Arsenic in that stomach. Although I'm not familiar with Gallium poisoning, I'm pretty sure everyone is familiar with Arsenic poisoning.
Cancer is a very long term concern if you're actively poisoning yourself with elemental Arsenic.
Slashdot Mirror
From March 30 2004:
http://news.slashdot.org/story/04/03/30/1435248/Spread-The-Love-And-Pay-Us
Yeah, "If".
Easy, in 1988 when McDonald's counter sues (and wins) against McSleep.
No, wait! Be extra careful with eunuchs-like systems!
CmdrTaco writes:
That reminds me of the time they signed away their book publishing rights and nearly lost the rights to their intellectual property and the name Penny Arcade. Except for that, I agree.
I'm a big PA fan, but they totally needed a business manager. And since I'm writing about him, I love this anecdote about Robert Khoo.
Wait, 2-digit year format? If you're having problems with the transition from "09" to "10", then you'd also have problems with the transition from "2009" to "2010". A Y2K-like bug would mean that the INPUT value is incomplete, or essentially pre-truncated. What you describe is code that intentionally truncates the value itself. The client had better not get any blame for this.
No, it's not. The premise of my scenario was "you're looking for someone in a city", meaning that you already know the identity of the individual.
Looking at the general issue that my example was trying to address, the 'whole point' is that most of the information overwhelming intelligence agencies is probably entirely irrelevant.
1. Having information expire before it is discovered follows practical usage of encryption.
2. Basically, an extra layer is being applied at the content level: slang and the like are just word substitution.
3. Too much information probably indicates that attention is being diverted to cover unnecessary discussions. Think of it this way: you're looking for someone in a city. You could wiretap a few people close to that person and hope you catch some bit of conversation OR you wiretap the whole city guaranteeing you have every bit of conversation. The first approach will offer information in real time while the second approach will take years to discover relevant information. The first approach is adopted for speed, while the only reason to adopt the second is for archiving.
FTA:
I have doubts about this - with the Panama canal under Allied control, getting to the east coast USA from Japan would have been VERY far-ranging.
Stealth bombers have one fundamental design problem - none have equally stealthy bomb bay doors, when open.
You get the stealth advantage going in, but now they see you and you better hope the non-stealthy parts are superior to the countermeasures of your opponent.
Inflammatory? You mean like:
Right, astronomical terms. On that scale, one could argue that Earth occupies an infinitesimally small volume so destroying it should be of only minor consequence as well.
How about we limit destructive tests to things that we have in multiple quantities?
In the meteorite marketplace, any that have hit a man-made object are significantly more valuable, given the rarity of such an occurrence.
A meteorite known to have hit a person would be even more so.
But anyone in such a position would be considered lucky if it doesn't kill them.
When I grind pawns, they sort of look like rooks. A decent upgrade, IMO. :)
That chart doesn't include 2006, 2007 or 2008.
30-Dec-2005: $8,170,424,541,313.62
29-Dec-2006: $8,680,224,380,086.18 (CY06 increase: +$509,799,838,772.56)
31-Dec-2007: $9,229,172,659,218.31 (CY07 increase: +$548,948,279,132.13)
31-Dec-2008: $10,699,804,864,612.13 (CY08 increase: +$1,470,632,205,393.82)
Source: www.publicdebt.ustreas.gov.
That CY08 number is close to TRIPLE the size of the maximum from that chart.
Your Sears Tower was already in place before that Democrat was sworn in.
There's one 'glitch' listed for Oblivion that is not: slaughterfish gasping.
A fish could spawn over land depending on the location of your load point - THAT issue should be the glitch.
But if it does appear over land, what do you expect a fish to do?
A gasping fish is an intentional feature, not a bug or glitch.
Sometimes we are blessed with the opportunity to provide real world examples.
In the case of FaceBook, the user grants certain content usage rights to FaceBook (presumably to advertise FaceBook itself).
In the linked example above, the user granted Creative Commons licensing to everyone.
Technically different, but it seems similar enough to properly illustrate your point.
By the way, this seems to be a follow up on that example.
The lesson: you give your privacy away, others will take it.
hmm... this game you describe sounds familiar...
Of course! A Roguelike game. Yeah, those are impossible.
My wizard puts on his robe and cornuthaum...
:)
I haven't played Starcraft online for a nearly a decade, so they may have patched my favorite strategy: using the Zerg Queen to parasite all available animals.
Since those units are never highlighted as hostile, players usually ignore them - killing them only if their presence interfered with a potential building site.
Once set, you'd have a bunch of covert spies all over the map. Flying animals were prized due to their mobility and were even less likely to be killed by players.
Your post reminds me of this PA comic.
I'm reminded of an even older slashdot story.
Is it ironic that the scientists of today chose to revolve the DNA evidence around him (his hair), instead of the son (his heir)?
:)
(AFAIK he had no children - jokes don't need to be accurate.)
Funny.
But I just realized something: "Please Please Me" was published in 1963, 45 years ago.
Technically, The Beatles IS grandpa's music!
Right here.
Between the years 2000 and 2005 I regularly drove a manual-shift 1988 Civic.
Even at 17 years old, that vehicle still averaged 45 mpg.
Applying this issue to just one LED is overreaching its significance, but the other comment was talking about many LEDs - increasing the overall amount of available surface area. Although, from what you say, it would take an awful lot of them to cause arsenic poisoning.
Actually, from what I understand, it would take about six 125mm wafers of GaAs to reach the LD50 for arsenic poisoning, if completely disassociated. That's a lot of material, all by itself.
Of course, it's probably safe to assume that the original comment referred to encased LEDs. If someone is eating encased LEDs, they'd most likely only encounter problems from the actual shape of the container (the metal leads in particular) as it passes through them so all this talk about etching becomes insignificant anyway.
While I'm moderately familiar with the general manufacturing process and the possibility of this specific hazard, I haven't been exposed to much of the practical side of manufacturing so I wasn't aware of the actual etching time frame. Thanks for the info.
Eating LEDs and you're worried about cancer?
How about this:
1. Acids are routinely used for wet etching GaAs - the crystal disassociates the two elements when exposed to acid.
2. Your stomach contains such acid - meaning we now have free floating Gallium and Arsenic in that stomach.
Although I'm not familiar with Gallium poisoning, I'm pretty sure everyone is familiar with Arsenic poisoning.
Cancer is a very long term concern if you're actively poisoning yourself with elemental Arsenic.