Well, to be fair, there are two broad classes of security bugs: minor bugs and major bugs. A minor bug is a buffer overflow or something in which the fix is obvious, trivial, and can be rolled out in an hour. A major bug is a bug in which the entire authentication system has to be thrown out and rewritten from scratch because it is trivially spoofed by replay attacks. Those sorts of bugs often can't be fixed in such a short time interval. On the other hand, those classes of failures are to some degree an indication that perhaps you shouldn't trust the company's software in general, so....
Exactly. The GP is seeing the world in black-and-white, where reality has many gradations in between.
Naive responsible disclosure: give it to the vendors. They do nothing. The bad guys figure it out. Everyone loses. Irresponsible disclosure: hand out a zero-day to the bad guys. Everyone loses. Effective responsible disclosure: disclose it to the vendors along with the promise to disclose it publicly on a scheduled date.
It should be noted that the third way is how CERT does things, and is the only way that the end users stand a chance of not getting screwed. It is important to make it clear that the vulnerability will be released to the public on that date no matter what. It is also important to make this date no more than two months in the future. Make the time frame too short and you're accused of creating a zero-day exploit. Make it too long and they won't bother looking at it until a week before, then they'll tell you that they can't fix it in time, and they'll accuse you of creating a zero-day exploit. There's a middle range in which it's close enough to scare the pants off of the manager types but far enough out that the fix can actually happen.
Most importantly, though, if the vendor doesn't fix it, you must disclose it anyway. Otherwise you lose all credibility, and vendors will simply put off fixing the problem because they'll assume that you will keep backing down.
Yeah. It's an okay show, but it's nowhere near what the previous shows were. It just doesn't have the right character dynamics. What characterized the previous Stargate shows (and I'll admit that this is formulaic, but it worked) was a smart aleck military guy, a geek (or several), and a strong female character. This show just has the geeks. And a strong military character. It's more BSG than Stargate.
Futurama. Think about Futurama reimagined in a younger, edgier style.
Fry: Chill, Hube. I'm like translating as fast as I can.
Leela: I'm so sick of being treated like some kind of object to be worshipped. I'm a real person with real feelings.
Young Zoidberg: You know, I don't think Mitchell likes me any more.
Leela: I'm pregnant.
...but typically is obvious after about 2-3 years.
Oh, and one last thing. Research has shown that in autistic kids, there is brain overgrowth relative to the size of the skull during the first 12 months, which is prior to any vaccinations. It's safe to say that there is *no* possibility that MMR causes autism....
This is easily solved. Autism can be detected as early as 14 months, but typically . Change the health standards to delay the MMR a year and if the age at which autism appears does not change, then it's unrelated. If it does, figure out why. There's not likely to be a substantive increase in deaths from kids getting the MMR at 2 1/2 versus 1 1/2, but changing those standards would likely put this unlikely theory of causation to rest permanently.
In other news, odds are good that almost 100% of IT staffers would say their data centers are understaffed. IT people (and geeks in general) tend not to say "no" until things are beyond what they can possibly handle. At this point, they're way beyond what should be considered "overloaded". Most managers are not from this group, so they don't comprehend that when we say we can handle something else, we often mean, "I'm superhuman and I can pull it off, but it's coming out of my stomach lining and you'd better recognize just how amazing I am for doing this."
The point of this article is that pneumatic tube networks are frelling cool, and they're old tech. To many persons of geeky persuasion (including me), this type of thing is fascinating.
Yeah, this just inspired me. When I build a house, I think I'm going to put in a pneumatic tube network. And I think I'm going to build a super-sized refrigerator with a robot arm. I think you can see where this is going....
I agree with you about it being an absolute age rather than a generational thing. When I was that age, I was much more likely to communicate with people frequently for non-work stuff. At the time, it was via talkers on the Internet. I had more close friends that I did stuff with than I do these days. That's a part of getting older. That said, that has always been true, and that's the very definition of a generation gap.
As for Facebook, I'd hardly call it "the latest cool". People who wouldn't have touched MySpace with a ten meter pole are on Facebook.... My parents are on Facebook. Almost my entire church choir is on Facebook, including the nun who directs it. It cuts across generational lines and makes lots of other communication mechanisms less important. Email is for work, FB is for friends---messaging, chatting, status, etc.
I think that in many ways, technology is breaking down the generation gap for those who are not too scared to keep up with it. I feel like there's much less generational difference between me and people a decade younger than I am than with people even three or four years older who didn't spend any significant amount of time with the Internet while in school. That said, ultimately the generational differences that do still exist are precisely the same ones that exist between any two generations, mostly stemming from where they are in their lives. People with kids are generally at a very different place than people who still are kids.
I kept wishing they would run into something or someone...
FTFY.
What always amuses me is people thinking that the whole "text speak" thing is a teenage thing. My subgeneration invented that when today's teenagers were in diapers. Heck, some of the old BBS abbreviations even predate my subgeneration.
Oh, and with regards to Nazi Germany, I think a closer parallel to the rethinking of the Versailles strategy would be Apple looking at the rise of Psystar and reconsidering policies, e.g. taking the stats about who installed Rebel EFI and on what hardware, then using that to figure out if there are ways to improve their product line to better attract those customers.
Of course, odds are, such info would be blindingly obvious in a completely useless way (e.g. "people are slapping it on cheap $200 beige boxes that they mostly cobbled together from parts of the now-defunct previous $200 beige box"), and as such, might not be all that helpful unless Apple decided to buy a PC maker and rebranded their products as low-end Macs under the Lemon brand name or something....:-D
Yeah, I did the math myself (thanks, Google). At a centimeter, assuming sea level, you'd have a time delay of 30 microseconds, give or take, or one sample at 34 kHz. At 48 kHz, a centimeter would be ever so slightly over one sample.
Here's the fun part: if you sum the two channels, that's essentially an inaudible delay from an acoustical perspective. If I'm thinking about it correctly, a delay of 1 sample is basically a simple comb filter whose first minimum is at the sampling rate, so the rolloff should be pretty small within the human hearing range. Of course, everything above half the sampling rate is already rolled off by the antialiasing filter in the ADC, so that would make the second microphone basically a no-op. Short of one element being just plain defective, you should not be able to perceive any major difference between a mono mix of the signals versus using one mic by itself.... Okay, maybe a few dB drop in the very top of your hearing range, but not much.
Well, that's not entirely true. A mono summing of the two signals without any gain correction would, by definition, be 6 dB hotter (double the voltage) without having to add any digital gain. So this could well be an attempt at working around inadequate preamplifier gain in the silicon. Just a guess, though. Or maybe they're trying to do some weird modeling thing to approximate a larger capsule with two smaller ones. Not sure if that's even possible, but it makes my head hurt thinking about it.:-D
No but the statistical probability of having someone with sufficient medical training is fairly high. On an airplane with 100 passengers (on the low side for most U.S. domestic flights), assuming that everyone flies with equal probability, your odds are as follows:
Doctor: 24.8%
RN: 80%
LPN: 23.3%
EMT: 20%
Paramedic: 4.73%
Firefighters with emergency medical training: 33.63%
Put another way, on average, you will have 1.87 trained medical personnel for a plane loaded with 100 people. Of course, this assumes that all Americans are equally likely to fly, all the way down to the homeless people. Since the affluent are statistically more likely to fly and medical people are generally paid above average wages, these numbers are probably understated.
And in an emergency, the flight crew can also get on the radio and reach a medical person on the ground almost instantly. Also, flight attendants are required to take medical training, which I believe does include training on emergency tracheostomies, but I'm not certain of that.
LOL. Well, in this case, there would actually be a real benefit to it being "stereo". When one mic shorts out, you still have a working mic (and a melted case, but...).
Yeah, stereo with a pair of such tiny mics side-by-side is pretty sad. You could get something approaching stereo by putting them on opposite ends of the laptop (spaced pair binaural). With a coincident pair, though, there's not much you can do without upping the capsule size significantly, AFAIK. If memory serves, once you start getting into capsules that are low-single-digit millimeters in diameter, even a cardioid capsule is going to behave like an omni at all but the highest audible frequencies.... This is all from memory, though, so I could be wrong.
Yes, I've seen the man pages. I've personally passed on several dozen bug reports in the OpenGL and GLUT man pages. Having reference documentation is well and good, but reference docs don't paint a complete picture by themselves. That's like trying to learn the English language by reading a dictionary.
Uh... what? A microphone, by definition, is an analog device. Please refer to this properly as a single-chip microphone and digital encoder package. No, I'm not just being pedantic. Twenty years of Sony and others selling "digital" headphones has made me a stickler for the proper use of the word "digital".:-)
There are surgical treatments that can get rid of the extreme obesity. Usually, when you lose enough weight, type II diabetes basically goes away on its own. The obesity is not caused by the diabetes. The diabetes is caused by the obesity. Admittedly, this is not always true (about 15% of people with type II diabetes are not obese), but it's usually a pretty safe bet. At a minimum, losing the weight will reduce the frequency of needing insulin injections, will make the diabetes more likely to be controllable through diet alone, and will reduce the risk of heart disease and numerous other health problems caused by inactivity brought on by severe obesity.
Seriously, if you're in the morbidly obese range, diabetic or not, you should look into gastric bypass surgery or other similar treatments. You might also consider eating more frequently, but eating smaller portions. This can significantly reduce weight without making you feel bad.
Fortunately, aircraft generally carry hydrocortisone, chlorpheniramine, and epinephrine for just such emergencies, and probably even a scalpel for an emergency in-flight tracheostomy if necessary. You're probably a heck of a lot safer on an airplane than you are on a bus in that regard.
OpenGL has an both a good documentation and extremely good literature
What's the URL? Paper books that cost money and are not easily searchable, not quickly cross-referenceable, not easily linked into discussion pages on the subject, etc. do not qualify as "good" documentation in this day and age. That might have been "good" in 1995. These days, the OpenGL documentation is an anachronism, no matter how well written it might be. As far as I'm concerned, if it's not HTML that I can link to, it doesn't exist, ergo OpenGL is largely undocumented.
By law, the manufacturers are required to have replacement parts for 7 years from the date of manufacture, at least in California (Song Beverly). I think there might be a U.S. equivalent in Magnuson Moss, but I'm not certain.
That's also forgetting that when you have an ISP granting a block of 8 IPs as many do, you lose 37.5% of your IPs to the network, broadcast, and router IPs. Granted, that's pretty much a worst case, but I suspect the percentage is still not small.
Plus you have IP ranges that aren't usable---0.x.x.x, 10.x.x.x 127.x.x.x, 169.254.x.x, 172.16.x.x through 172.31.x.x, 192.168.x.x, 224.x.x.x through 239.x.x.x, and 255.x.x.x. That's about 7.8% of the usable address space by itself.
Slashdot Mirror
Well, to be fair, there are two broad classes of security bugs: minor bugs and major bugs. A minor bug is a buffer overflow or something in which the fix is obvious, trivial, and can be rolled out in an hour. A major bug is a bug in which the entire authentication system has to be thrown out and rewritten from scratch because it is trivially spoofed by replay attacks. Those sorts of bugs often can't be fixed in such a short time interval. On the other hand, those classes of failures are to some degree an indication that perhaps you shouldn't trust the company's software in general, so....
Exactly. The GP is seeing the world in black-and-white, where reality has many gradations in between.
Naive responsible disclosure: give it to the vendors. They do nothing. The bad guys figure it out. Everyone loses.
Irresponsible disclosure: hand out a zero-day to the bad guys. Everyone loses.
Effective responsible disclosure: disclose it to the vendors along with the promise to disclose it publicly on a scheduled date.
It should be noted that the third way is how CERT does things, and is the only way that the end users stand a chance of not getting screwed. It is important to make it clear that the vulnerability will be released to the public on that date no matter what. It is also important to make this date no more than two months in the future. Make the time frame too short and you're accused of creating a zero-day exploit. Make it too long and they won't bother looking at it until a week before, then they'll tell you that they can't fix it in time, and they'll accuse you of creating a zero-day exploit. There's a middle range in which it's close enough to scare the pants off of the manager types but far enough out that the fix can actually happen.
Most importantly, though, if the vendor doesn't fix it, you must disclose it anyway. Otherwise you lose all credibility, and vendors will simply put off fixing the problem because they'll assume that you will keep backing down.
Yeah. It's an okay show, but it's nowhere near what the previous shows were. It just doesn't have the right character dynamics. What characterized the previous Stargate shows (and I'll admit that this is formulaic, but it worked) was a smart aleck military guy, a geek (or several), and a strong female character. This show just has the geeks. And a strong military character. It's more BSG than Stargate.
D'oh. Forgot to change one of the names and fix errors in the original quote. Make that
You know, I don't think Bender likes me anymore.
*sigh*
Futurama. Think about Futurama reimagined in a younger, edgier style.
Fry: Chill, Hube. I'm like translating as fast as I can.
Leela: I'm so sick of being treated like some kind of object to be worshipped. I'm a real person with real feelings.
Young Zoidberg: You know, I don't think Mitchell likes me any more.
Leela: I'm pregnant.
[Everyone]: No.
With apologies to Stargate.
Oops. Forgot to finish the first sentence.
...but typically is obvious after about 2-3 years.
Oh, and one last thing. Research has shown that in autistic kids, there is brain overgrowth relative to the size of the skull during the first 12 months, which is prior to any vaccinations. It's safe to say that there is *no* possibility that MMR causes autism....
This is easily solved. Autism can be detected as early as 14 months, but typically . Change the health standards to delay the MMR a year and if the age at which autism appears does not change, then it's unrelated. If it does, figure out why. There's not likely to be a substantive increase in deaths from kids getting the MMR at 2 1/2 versus 1 1/2, but changing those standards would likely put this unlikely theory of causation to rest permanently.
In other news, odds are good that almost 100% of IT staffers would say their data centers are understaffed. IT people (and geeks in general) tend not to say "no" until things are beyond what they can possibly handle. At this point, they're way beyond what should be considered "overloaded". Most managers are not from this group, so they don't comprehend that when we say we can handle something else, we often mean, "I'm superhuman and I can pull it off, but it's coming out of my stomach lining and you'd better recognize just how amazing I am for doing this."
Yeah, this just inspired me. When I build a house, I think I'm going to put in a pneumatic tube network. And I think I'm going to build a super-sized refrigerator with a robot arm. I think you can see where this is going....
Computer, make me a sammich.
bzzt, bzzt, bzzt, bzzt. Thuck... ssssssshhhhhhhhhhh... thuck.
Mmmm.
Orange juice, please.
Bzzzzt. Clunk. Bzzzzzzzzzzzzt. Clunk. Bzt. Thuck... ssssshhhhh... thuck.
*Pours into glass, places OJ bottle back into canister*
Thuck... ssssssssshhhhhhh... thuck. Bzzt. Clunk. Bzzzzzzzzzzzt. Clunk. Bzzzzt.
I agree with you about it being an absolute age rather than a generational thing. When I was that age, I was much more likely to communicate with people frequently for non-work stuff. At the time, it was via talkers on the Internet. I had more close friends that I did stuff with than I do these days. That's a part of getting older. That said, that has always been true, and that's the very definition of a generation gap.
As for Facebook, I'd hardly call it "the latest cool". People who wouldn't have touched MySpace with a ten meter pole are on Facebook.... My parents are on Facebook. Almost my entire church choir is on Facebook, including the nun who directs it. It cuts across generational lines and makes lots of other communication mechanisms less important. Email is for work, FB is for friends---messaging, chatting, status, etc.
I think that in many ways, technology is breaking down the generation gap for those who are not too scared to keep up with it. I feel like there's much less generational difference between me and people a decade younger than I am than with people even three or four years older who didn't spend any significant amount of time with the Internet while in school. That said, ultimately the generational differences that do still exist are precisely the same ones that exist between any two generations, mostly stemming from where they are in their lives. People with kids are generally at a very different place than people who still are kids.
FTFY.
What always amuses me is people thinking that the whole "text speak" thing is a teenage thing. My subgeneration invented that when today's teenagers were in diapers. Heck, some of the old BBS abbreviations even predate my subgeneration.
Don't forget IV drug abuse.
Oh, and with regards to Nazi Germany, I think a closer parallel to the rethinking of the Versailles strategy would be Apple looking at the rise of Psystar and reconsidering policies, e.g. taking the stats about who installed Rebel EFI and on what hardware, then using that to figure out if there are ways to improve their product line to better attract those customers.
Of course, odds are, such info would be blindingly obvious in a completely useless way (e.g. "people are slapping it on cheap $200 beige boxes that they mostly cobbled together from parts of the now-defunct previous $200 beige box"), and as such, might not be all that helpful unless Apple decided to buy a PC maker and rebranded their products as low-end Macs under the Lemon brand name or something.... :-D
If your movements are rouge, you'd better get that checked. It's probably just hemorrhoids, but it could be a sign of colon cancer....
Ba-dump bump.
Yeah, I did the math myself (thanks, Google). At a centimeter, assuming sea level, you'd have a time delay of 30 microseconds, give or take, or one sample at 34 kHz. At 48 kHz, a centimeter would be ever so slightly over one sample.
Here's the fun part: if you sum the two channels, that's essentially an inaudible delay from an acoustical perspective. If I'm thinking about it correctly, a delay of 1 sample is basically a simple comb filter whose first minimum is at the sampling rate, so the rolloff should be pretty small within the human hearing range. Of course, everything above half the sampling rate is already rolled off by the antialiasing filter in the ADC, so that would make the second microphone basically a no-op. Short of one element being just plain defective, you should not be able to perceive any major difference between a mono mix of the signals versus using one mic by itself.... Okay, maybe a few dB drop in the very top of your hearing range, but not much.
Well, that's not entirely true. A mono summing of the two signals without any gain correction would, by definition, be 6 dB hotter (double the voltage) without having to add any digital gain. So this could well be an attempt at working around inadequate preamplifier gain in the silicon. Just a guess, though. Or maybe they're trying to do some weird modeling thing to approximate a larger capsule with two smaller ones. Not sure if that's even possible, but it makes my head hurt thinking about it. :-D
No but the statistical probability of having someone with sufficient medical training is fairly high. On an airplane with 100 passengers (on the low side for most U.S. domestic flights), assuming that everyone flies with equal probability, your odds are as follows:
Doctor: 24.8%
RN: 80%
LPN: 23.3%
EMT: 20%
Paramedic: 4.73%
Firefighters with emergency medical training: 33.63%
Put another way, on average, you will have 1.87 trained medical personnel for a plane loaded with 100 people. Of course, this assumes that all Americans are equally likely to fly, all the way down to the homeless people. Since the affluent are statistically more likely to fly and medical people are generally paid above average wages, these numbers are probably understated.
And in an emergency, the flight crew can also get on the radio and reach a medical person on the ground almost instantly. Also, flight attendants are required to take medical training, which I believe does include training on emergency tracheostomies, but I'm not certain of that.
LOL. Well, in this case, there would actually be a real benefit to it being "stereo". When one mic shorts out, you still have a working mic (and a melted case, but...).
Yeah, stereo with a pair of such tiny mics side-by-side is pretty sad. You could get something approaching stereo by putting them on opposite ends of the laptop (spaced pair binaural). With a coincident pair, though, there's not much you can do without upping the capsule size significantly, AFAIK. If memory serves, once you start getting into capsules that are low-single-digit millimeters in diameter, even a cardioid capsule is going to behave like an omni at all but the highest audible frequencies.... This is all from memory, though, so I could be wrong.
And now you understand why we call it "security theater". It is Shakespearean---full of sound and fury, securing nothing.
Yes, I've seen the man pages. I've personally passed on several dozen bug reports in the OpenGL and GLUT man pages. Having reference documentation is well and good, but reference docs don't paint a complete picture by themselves. That's like trying to learn the English language by reading a dictionary.
Uh... what? A microphone, by definition, is an analog device. Please refer to this properly as a single-chip microphone and digital encoder package. No, I'm not just being pedantic. Twenty years of Sony and others selling "digital" headphones has made me a stickler for the proper use of the word "digital". :-)
There are surgical treatments that can get rid of the extreme obesity. Usually, when you lose enough weight, type II diabetes basically goes away on its own. The obesity is not caused by the diabetes. The diabetes is caused by the obesity. Admittedly, this is not always true (about 15% of people with type II diabetes are not obese), but it's usually a pretty safe bet. At a minimum, losing the weight will reduce the frequency of needing insulin injections, will make the diabetes more likely to be controllable through diet alone, and will reduce the risk of heart disease and numerous other health problems caused by inactivity brought on by severe obesity.
Seriously, if you're in the morbidly obese range, diabetic or not, you should look into gastric bypass surgery or other similar treatments. You might also consider eating more frequently, but eating smaller portions. This can significantly reduce weight without making you feel bad.
Fortunately, aircraft generally carry hydrocortisone, chlorpheniramine, and epinephrine for just such emergencies, and probably even a scalpel for an emergency in-flight tracheostomy if necessary. You're probably a heck of a lot safer on an airplane than you are on a bus in that regard.
What's the URL? Paper books that cost money and are not easily searchable, not quickly cross-referenceable, not easily linked into discussion pages on the subject, etc. do not qualify as "good" documentation in this day and age. That might have been "good" in 1995. These days, the OpenGL documentation is an anachronism, no matter how well written it might be. As far as I'm concerned, if it's not HTML that I can link to, it doesn't exist, ergo OpenGL is largely undocumented.
By law, the manufacturers are required to have replacement parts for 7 years from the date of manufacture, at least in California (Song Beverly). I think there might be a U.S. equivalent in Magnuson Moss, but I'm not certain.
That's also forgetting that when you have an ISP granting a block of 8 IPs as many do, you lose 37.5% of your IPs to the network, broadcast, and router IPs. Granted, that's pretty much a worst case, but I suspect the percentage is still not small.
Plus you have IP ranges that aren't usable---0.x.x.x, 10.x.x.x 127.x.x.x, 169.254.x.x, 172.16.x.x through 172.31.x.x, 192.168.x.x, 224.x.x.x through 239.x.x.x, and 255.x.x.x. That's about 7.8% of the usable address space by itself.