Any mechanical design that results in failure due to a speed change of 6% was prone to failure anyway. I was expecting a more sophisticated attack that would deliver process failure rather than a mechanical failure.
The term from mechanical engineering that you don't know to google / wikipedia for, is "critical speed" or for that matter "Rotordynamics" in general.
If the only limiting parameter is critical shaft speed, and "everyone knows" you can very reliably measure time / rotation speed to less than parts per billion, you wanna run right up to the limit of mechanical Q and manufacturing tolerance. Running at 6% below is ridiculously sloppy engineering, especially if process efficiency might scale as square or cube of RPM or maybe worse.
"Everyone knows" you can trust timing measurements, at least in this modern era, to way under parts per billion. Screwing up that assumption by 6% is actually an extremely sophisticated attack.
When Germany tried that stunt with Poland, a world war started.
Back to history class for you, we were talking about:
blow up someone you think could probably some day maybe consider thinking about attacking you.
Now, that logic IS perfectly valid for the Pearl Harbor incident.
You could possibly argue absolutely everything that happened in WWII previous to Operation Barbarossa was merely the preparation for Operation Barbarossa, and Poland did happen first, so maybe on a very extreme ultra extended technicality you are sorta tangentially correct.... Naah stick to using Pearl Harbor for an example of your thesis.
The entire thing is a big ball of outdated SCADA systems held together with bubble gum and bailing wire. It can barely handle a couple fault on a hot day let alone a concerted attack (see the great NE blackout of 2003).
How could maximizing profit in a deregulated market not be the holy grail and goal of all human activity? If maximizing profit means California or NYC goes dark on occasion, so be it.
You make it sound different from absolutely every other complicated technological system in the entire capitalist world economy. Other than they happen to be delivering KWh, instead of landing aircraft, pumping drinking water, delivering food, or refining fuel.
You act as if people are willing to differentiate the two...
"are willing to" vs "can"? I think the latter is far more realistic.
This is a funny area to discuss, because my opinion simply doesn't matter, the act of pointing out this fact almost universally results in people assuming I oppose their personal strongly held beliefs, regardless of which side they happen to be on. Bet I get a flame or troll moderation / comment from both sides.
Which brings us back to why the original post was a rather bad idea:
the simplest one being barricaded somewhere on a mountain
Worst possibly situation is getting "tree-d" like that. Modern siege warfare extremely strongly favors the attacker, if for no other reason than incredibly efficient modern logistical supply. Unless you've got more than half the world supply of... everything... on the mountain with you when you get treed.
Hmmm. I've got a stunning idea! How bout not plug your centrifuge into a PC based ethernet network?
My doctors blood centrifuge does not have an ethernet port. Nor does my dentist's xray machine. Nor my doctors stethoscope, nor that hammer thingy they hit your knee with to test your reflexes.
The argument used to be that the DSP based controller software required to balance the rotor required a rather high end server grade PC at least $3000 worth of pentium 75s, so we need to spread that PC cost across multiple centrifuges. The problem is I can get better DSP performance out of a five dollar PIC microcontroller now. And they'll never be susceptible to an external attack, so why bother with firewalls and who cares if they are on ethernet with the modern equivalent of typhoid mary, the standard PC.
Who will win, the hardware guys whom make cheap ethernet interfaces, or the hardware guys whom make cheap microcontroller hardware? In some cases, same company different departments?
Now if they blew up something that inherently must be decentralized like an electrical grid, then we'd have a (slight) puzzle.
If the current cheap phones had perfect support for 3d-holos of the caller for free already today, I still wouldn't really use it...
I'd use it just as much as the free videoconferencing software on my desktop... One time, oh isn't that cool technology, well that was interesting, goodbye. And never again.
I'm asssuming the laser pointer drew excessive current, and thus used up all the air in the batteries. Then when off for a few seconds, more air was able to diffuse in through holes, "recharging" them. I also imagine that once their seals were broken, they would degrade the electrodes after a week or so, even if not used.
The funny part is you missed the point of your parent post... they're specifically engineered to dump about a milliamp for a week into an "in ear" hearing aid. Low short circuit current / high internal resistance is actually considered an intrinsically safe feature, it is impossible to burn your ear or set your hair on fire. Personally I would not want a LiPoly or nicad battery in my ear.
Another part thats cool is that if the seal is not broken, they'll theoretically keep "forever" certainly longer than even lithium primary cells. Maybe decades. You can buy a multi-year supply if you get a good deal, and as long as you don't unpeel the tape seal, they'll have 100% capacity. The only thing that will kill them is intense vibration... car glove compartment would be a very bad place for spare zinc-air batteries.
You could re-engineer that battery chemistry into being able to dump kiloamps if you wanted, would probably require forced air and an O2 sensor to make sure humans don't suffocate like some kerosene heaters have. But the market forced that specific battery chemistry into the hearing aide sub-market, so you simply can not buy low internal resistance / high capacity zinc-air batteries.
Are holograms visible outside? Because I'd really appreciate a cell phone that was usable in the sun.
When you're driving at night, they'll work fine, although I agree when driving during the day it could be annoying. Other than driving, why would I go out in the sun and get skin cancer?
Because for many, the cell phone will be their desktop and laptop.
Why would anyone want to work on multiple 20 inch screens with an ergonomic keyboard and mouse, when they could use a teeny tiny little cellphone instead? God knows whenever I'm in a CAD app or working on a text document (including source code), I always wish I had a smaller screen. Also whenever I have a nice keyboard, like an IBM model M, I always wish I could use my Atari400 style cellphone membrane keypad instead.
This also explains the industry wide utter dominance of tiny commuter cars over those obese SUVs that no one buys.
I bet in the future there may be a way to make Linux work with drivers my scanner. Just a prediction. I know it's way out there.
The mistake you made was buying a "$my" brand scanner, for your local value of "$my". Or "my $my;"
Brother MFC devices that include a scanner work right out of the box on linux. On windows you need to download some bloatware app, not the worst I've ever seen, but it does nicely slow down boot times. On my tiny herd of macs (just a breeding pair) the bloated app was, if I recall correctly, optional, and we never reboot the macs, thus slower booting is irrelevant (said in best 7 of 9 voice). So linux was the simplest, then mac, then windows.
Daily builds have never made much sense to me.... If you have expensive (processing-wise) unit tests
Some places use expensive (angry-customer-wise and lost-sales-wise) "unit tests". Life is never easy in operations or the call center, but at least they know if it breaks at 2:36pm it almost certainly has to be an operations problem as opposed to a failed deployment.
Also important for rolling out new features simultaneously with marketing/sales. Or having a formal way to cease new rollouts before the big fundraising round demonstration (of course stopping regular deployment merely means you'll be demoing what happens when all the memory leaks out and swap space fills, or transaction logs or whatever local equivalent)
The "nobody takes this seriously part" requires relating the 1991 date of the quote with MS buying Fox Technologies in 1992, along with their product Visual FoxPro, which I am told was renamed to "Access" and released in 1992.
You won't get anything usable from an end user without some severe filtering.
The two quotes are more closely related than you'd think, in that both are limited to extremely narrow experiences and assume the rest of the world MUST be the same as the past limited experiences.
If all I have is a hammer, suspiciously, everything, including bolts and screws, looks like a nail.
Also, I don't want end customers submitting directly into my bug tracker.
You mean, you don't want then submitting directly into your queue. OK who cares. Why force Q/A to manually retype or cut-n-paste each customer request before dropping the ticket in your queue? Its not as if cut-n-paste magically improves upon pasting. Trust me, Q/A doesn't necessarily make any more sense than customer speak, but being distant from a bug does mean small details will be lost, some of which may be important.
I would never, ever let a customer set the actual ticket severity. They are free to enter their opinion in a separate "customer severity" field, which you might even pay attention to, or perhaps not. I would also never let the customer see the actual severity; "customer's reported severity" field, sure, but never your actual internal prioritization. Don't pretty much all post 1980 ticketing systems work that way?
There has to be a gain that measurably outweighs the inconveniences.
Not necessarily a gain, but a DCVS like git inherently "backs up everything that is needed or ever happened" to all the devs.
1) Ultimate multiple site backup capacity for disaster recovery
2) If engineered properly, bringing up another host in the cluster / bringing up a disaster recovery site is beyond trivial.
3) (the bad news) Security FreakOut!
If the big boss says this shall be a small component of the disaster recovery plan, well, then an abstract weekly metric result doesn't much matter, does it?
The other problem is the update article is inherently self contradictory. "Do you use a distributed source control system" vs "freedom to choose development software". So... free to choose, as long as someone with limited experience thinks you're making the only correct choice for all possible situations?
Motorola filed another suit in the Western District of Wisconsin,
How exactly does that work? Thats only 100 miles to the west of me, and I enjoy the bike paths along the Mississippi river, and the only upper midwestern cave that being the cave of the mounds, and... uh... thats about it for high technology in the western "half" of the state. Now don't get me wrong, Chippewa Falls was THE place to be technologically about three decades ago for obvious reasons and I want to visit the CFMIT someday, which is claimed to be better than Chicago's kid oriented museum of science and industry, but other than that...
Is the plan something like the defendants don't own snowmobiles and ATVs, so they won't be able to get to the courthouse, so we have a guaranteed win?
I am not at all convinced that getting the government involved will improve my life.
The government and the corporations have merged. There are some interdepartmental budget squabbles, but by in large, one happy family out to get us. After accepting that, your last line no longer contains any meaning.
But the problem with having regulation is that, eventually, the "keeper of the net" will become corrupt and find ways to control the flow of data and get rich doing so or worse yet be controlled by the government.
And the end result of no regulation would be different... how exactly? Same corruption just a little less transparent about how its done?
Traffic shaping on the last mile is only going to have limited benefit. Unless you're suggesting a complete fiber GamerNet backbone - it still goes over the same backbones as the other ISP's are sharing already.
Another solution is to force the MTU to a minimum value at the endpoints. Small MTU means low latency and great interleaving of packets. It also means hideous packet per second results, but theoretically "GamerNet" can afford gear that laughs at hideous packet per second counts.
Small packets also increase overhead lowering overall thruput. No problemo, give them more bandwidth to make up for the losses in small packets, after all "GamerNet" is a premium service.
None of these GamerNet features would require backbone cooperation, although the PPS problem might piss off their provider (but, GamerNet has the cash to convince them its OK)
Its not as crazy or +1 funny as you might think, as GamerNet would make a great 9-5 business videoconferencing and voip service, and you can charge the heck out of those guys. Then 5-9 you sell the same capacity to gamers. Maybe market it as a premium service for work at homers during the day and WOWers during the night. It could happen.
shouldn't the Internet remain free from regulation?"
So.. My P.U.C. regulated monopoly telco raised some federal reserve regulated money on the SEC regulated stock exchange to buy some FCC regulated DSL headend gear to connect to my locally regulated monopoly phone lines which run to my HOA and zoning board regulated house where plug in my FCC regulated DSL modem so as to access my trademark and copyright office regulated domain name web sites, as I chow down on my FDA regulated cheetos while drinking some EPA regulated water from my local public utility in an effort to see some FTC regulated pr0n on the intertubes.
All that and the phone company wants to mess with my connection, but the govt can't stop them, because THAT would be "too much regulation". What a steaming pile.
Of course I just direct them to Bank of America that has a special "illegals" program for opening accounts for people that otherwise can't have bank accounts. It is great for drug dealers, undocumented immigrants and thieves looking to launder money. Thanks, BofA, you're a great help.
That is one well known financial industry equivalent of a honeypot... There are others.
Do you mean illegal now, or illegal later? How can I know what will be illegal later, and thus protect myself now?
You can understand why certain ethnic groups in Germany might be nervous at the idea of providing a financial record of all menorahs ever sold, even if at this point they are certainly currently legal. Who benefits from that kind of record? The people or the state?
Same story different country and decade with ammo, alcohol, tobacco, certain firearm components, jtag smart card interfaces, gold coins...
Slashdot Mirror
Any mechanical design that results in failure due to a speed change of 6% was prone to failure anyway. I was expecting a more sophisticated attack that would deliver process failure rather than a mechanical failure.
The term from mechanical engineering that you don't know to google / wikipedia for, is "critical speed" or for that matter "Rotordynamics" in general.
If the only limiting parameter is critical shaft speed, and "everyone knows" you can very reliably measure time / rotation speed to less than parts per billion, you wanna run right up to the limit of mechanical Q and manufacturing tolerance. Running at 6% below is ridiculously sloppy engineering, especially if process efficiency might scale as square or cube of RPM or maybe worse.
"Everyone knows" you can trust timing measurements, at least in this modern era, to way under parts per billion. Screwing up that assumption by 6% is actually an extremely sophisticated attack.
ZING!
And I have to ask, why the heck does removable media still have so many vulnerabilities?
It doesn't have vulnerabilities. On my box, /etc/fstab has noexec for usb sticks. Besides, an AMD64 port binary won't do too much on my i386 port.
Oh you mean on Windows. That's mistake #1 right there.
When Germany tried that stunt with Poland, a world war started.
Back to history class for you, we were talking about:
blow up someone you think could probably some day maybe consider thinking about attacking you.
Now, that logic IS perfectly valid for the Pearl Harbor incident.
You could possibly argue absolutely everything that happened in WWII previous to Operation Barbarossa was merely the preparation for Operation Barbarossa, and Poland did happen first, so maybe on a very extreme ultra extended technicality you are sorta tangentially correct.... Naah stick to using Pearl Harbor for an example of your thesis.
The entire thing is a big ball of outdated SCADA systems held together with bubble gum and bailing wire. It can barely handle a couple fault on a hot day let alone a concerted attack (see the great NE blackout of 2003).
How could maximizing profit in a deregulated market not be the holy grail and goal of all human activity? If maximizing profit means California or NYC goes dark on occasion, so be it.
You make it sound different from absolutely every other complicated technological system in the entire capitalist world economy. Other than they happen to be delivering KWh, instead of landing aircraft, pumping drinking water, delivering food, or refining fuel.
You act as if people are willing to differentiate the two...
"are willing to" vs "can"? I think the latter is far more realistic.
This is a funny area to discuss, because my opinion simply doesn't matter, the act of pointing out this fact almost universally results in people assuming I oppose their personal strongly held beliefs, regardless of which side they happen to be on. Bet I get a flame or troll moderation / comment from both sides.
they will hunt you down
Which brings us back to why the original post was a rather bad idea:
the simplest one being barricaded somewhere on a mountain
Worst possibly situation is getting "tree-d" like that. Modern siege warfare extremely strongly favors the attacker, if for no other reason than incredibly efficient modern logistical supply. Unless you've got more than half the world supply of ... everything ... on the mountain with you when you get treed.
I wonder how cyber defense will counter it.
Hmmm. I've got a stunning idea! How bout not plug your centrifuge into a PC based ethernet network?
My doctors blood centrifuge does not have an ethernet port. Nor does my dentist's xray machine. Nor my doctors stethoscope, nor that hammer thingy they hit your knee with to test your reflexes.
The argument used to be that the DSP based controller software required to balance the rotor required a rather high end server grade PC at least $3000 worth of pentium 75s, so we need to spread that PC cost across multiple centrifuges. The problem is I can get better DSP performance out of a five dollar PIC microcontroller now. And they'll never be susceptible to an external attack, so why bother with firewalls and who cares if they are on ethernet with the modern equivalent of typhoid mary, the standard PC.
Who will win, the hardware guys whom make cheap ethernet interfaces, or the hardware guys whom make cheap microcontroller hardware? In some cases, same company different departments?
Now if they blew up something that inherently must be decentralized like an electrical grid, then we'd have a (slight) puzzle.
If the current cheap phones had perfect support for 3d-holos of the caller for free already today, I still wouldn't really use it...
I'd use it just as much as the free videoconferencing software on my desktop...
One time, oh isn't that cool technology, well that was interesting, goodbye. And never again.
I'm asssuming the laser pointer drew excessive current, and thus used up all the air in the batteries. Then when off for a few seconds, more air was able to diffuse in through holes, "recharging" them. I also imagine that once their seals were broken, they would degrade the electrodes after a week or so, even if not used.
The funny part is you missed the point of your parent post... they're specifically engineered to dump about a milliamp for a week into an "in ear" hearing aid. Low short circuit current / high internal resistance is actually considered an intrinsically safe feature, it is impossible to burn your ear or set your hair on fire. Personally I would not want a LiPoly or nicad battery in my ear.
Another part thats cool is that if the seal is not broken, they'll theoretically keep "forever" certainly longer than even lithium primary cells. Maybe decades. You can buy a multi-year supply if you get a good deal, and as long as you don't unpeel the tape seal, they'll have 100% capacity. The only thing that will kill them is intense vibration ... car glove compartment would be a very bad place for spare zinc-air batteries.
You could re-engineer that battery chemistry into being able to dump kiloamps if you wanted, would probably require forced air and an O2 sensor to make sure humans don't suffocate like some kerosene heaters have. But the market forced that specific battery chemistry into the hearing aide sub-market, so you simply can not buy low internal resistance / high capacity zinc-air batteries.
Are holograms visible outside? Because I'd really appreciate a cell phone that was usable in the sun.
When you're driving at night, they'll work fine, although I agree when driving during the day it could be annoying. Other than driving, why would I go out in the sun and get skin cancer?
Because for many, the cell phone will be their desktop and laptop.
Why would anyone want to work on multiple 20 inch screens with an ergonomic keyboard and mouse, when they could use a teeny tiny little cellphone instead? God knows whenever I'm in a CAD app or working on a text document (including source code), I always wish I had a smaller screen. Also whenever I have a nice keyboard, like an IBM model M, I always wish I could use my Atari400 style cellphone membrane keypad instead.
This also explains the industry wide utter dominance of tiny commuter cars over those obese SUVs that no one buys.
I bet in the future there may be a way to make Linux work with drivers my scanner. Just a prediction. I know it's way out there.
The mistake you made was buying a "$my" brand scanner, for your local value of "$my". Or "my $my;"
Brother MFC devices that include a scanner work right out of the box on linux. On windows you need to download some bloatware app, not the worst I've ever seen, but it does nicely slow down boot times. On my tiny herd of macs (just a breeding pair) the bloated app was, if I recall correctly, optional, and we never reboot the macs, thus slower booting is irrelevant (said in best 7 of 9 voice). So linux was the simplest, then mac, then windows.
Unfortunately ethanol requires even more land use, in an already overcrowded planet.
And the other problem is it takes two barrels of crude equivalent to manufacture one ethanol equivalent of a barrel of oil.
Daily builds have never made much sense to me. ... If you have expensive (processing-wise) unit tests
Some places use expensive (angry-customer-wise and lost-sales-wise) "unit tests". Life is never easy in operations or the call center, but at least they know if it breaks at 2:36pm it almost certainly has to be an operations problem as opposed to a failed deployment.
Also important for rolling out new features simultaneously with marketing/sales. Or having a formal way to cease new rollouts before the big fundraising round demonstration (of course stopping regular deployment merely means you'll be demoing what happens when all the memory leaks out and swap space fills, or transaction logs or whatever local equivalent)
The "nobody takes this seriously part" requires relating the 1991 date of the quote with MS buying Fox Technologies in 1992, along with their product Visual FoxPro, which I am told was renamed to "Access" and released in 1992.
his list of requirements for good development
You won't get anything usable from an end user without some severe filtering.
The two quotes are more closely related than you'd think, in that both are limited to extremely narrow experiences and assume the rest of the world MUST be the same as the past limited experiences.
If all I have is a hammer, suspiciously, everything, including bolts and screws, looks like a nail.
Also, I don't want end customers submitting directly into my bug tracker.
You mean, you don't want then submitting directly into your queue. OK who cares. Why force Q/A to manually retype or cut-n-paste each customer request before dropping the ticket in your queue? Its not as if cut-n-paste magically improves upon pasting. Trust me, Q/A doesn't necessarily make any more sense than customer speak, but being distant from a bug does mean small details will be lost, some of which may be important.
I would never, ever let a customer set the actual ticket severity. They are free to enter their opinion in a separate "customer severity" field, which you might even pay attention to, or perhaps not. I would also never let the customer see the actual severity; "customer's reported severity" field, sure, but never your actual internal prioritization. Don't pretty much all post 1980 ticketing systems work that way?
There has to be a gain that measurably outweighs the inconveniences.
Not necessarily a gain, but a DCVS like git inherently "backs up everything that is needed or ever happened" to all the devs.
1) Ultimate multiple site backup capacity for disaster recovery
2) If engineered properly, bringing up another host in the cluster / bringing up a disaster recovery site is beyond trivial.
3) (the bad news) Security FreakOut!
If the big boss says this shall be a small component of the disaster recovery plan, well, then an abstract weekly metric result doesn't much matter, does it?
The other problem is the update article is inherently self contradictory. "Do you use a distributed source control system" vs "freedom to choose development software". So... free to choose, as long as someone with limited experience thinks you're making the only correct choice for all possible situations?
Motorola filed another suit in the Western District of Wisconsin,
How exactly does that work? Thats only 100 miles to the west of me, and I enjoy the bike paths along the Mississippi river, and the only upper midwestern cave that being the cave of the mounds, and ... uh ... thats about it for high technology in the western "half" of the state. Now don't get me wrong, Chippewa Falls was THE place to be technologically about three decades ago for obvious reasons and I want to visit the CFMIT someday, which is claimed to be better than Chicago's kid oriented museum of science and industry, but other than that...
Is the plan something like the defendants don't own snowmobiles and ATVs, so they won't be able to get to the courthouse, so we have a guaranteed win?
I am not at all convinced that getting the government involved will improve my life.
The government and the corporations have merged. There are some interdepartmental budget squabbles, but by in large, one happy family out to get us. After accepting that, your last line no longer contains any meaning.
But the problem with having regulation is that, eventually, the "keeper of the net" will become corrupt and find ways to control the flow of data and get rich doing so or worse yet be controlled by the government.
And the end result of no regulation would be different ... how exactly? Same corruption just a little less transparent about how its done?
Traffic shaping on the last mile is only going to have limited benefit. Unless you're suggesting a complete fiber GamerNet backbone - it still goes over the same backbones as the other ISP's are sharing already.
Another solution is to force the MTU to a minimum value at the endpoints. Small MTU means low latency and great interleaving of packets. It also means hideous packet per second results, but theoretically "GamerNet" can afford gear that laughs at hideous packet per second counts.
Small packets also increase overhead lowering overall thruput. No problemo, give them more bandwidth to make up for the losses in small packets, after all "GamerNet" is a premium service.
None of these GamerNet features would require backbone cooperation, although the PPS problem might piss off their provider (but, GamerNet has the cash to convince them its OK)
Its not as crazy or +1 funny as you might think, as GamerNet would make a great 9-5 business videoconferencing and voip service, and you can charge the heck out of those guys. Then 5-9 you sell the same capacity to gamers. Maybe market it as a premium service for work at homers during the day and WOWers during the night. It could happen.
shouldn't the Internet remain free from regulation?"
So.. My P.U.C. regulated monopoly telco raised some federal reserve regulated money on the SEC regulated stock exchange to buy some FCC regulated DSL headend gear to connect to my locally regulated monopoly phone lines which run to my HOA and zoning board regulated house where plug in my FCC regulated DSL modem so as to access my trademark and copyright office regulated domain name web sites, as I chow down on my FDA regulated cheetos while drinking some EPA regulated water from my local public utility in an effort to see some FTC regulated pr0n on the intertubes.
All that and the phone company wants to mess with my connection, but the govt can't stop them, because THAT would be "too much regulation". What a steaming pile.
Of course I just direct them to Bank of America that has a special "illegals" program for opening accounts for people that otherwise can't have bank accounts. It is great for drug dealers, undocumented immigrants and thieves looking to launder money. Thanks, BofA, you're a great help.
That is one well known financial industry equivalent of a honeypot ... There are others.
Why do you need to make anonymous transactions?
Ohhhh. You mean illegal transactions.
Do you mean illegal now, or illegal later? How can I know what will be illegal later, and thus protect myself now?
You can understand why certain ethnic groups in Germany might be nervous at the idea of providing a financial record of all menorahs ever sold, even if at this point they are certainly currently legal. Who benefits from that kind of record? The people or the state?
Same story different country and decade with ammo, alcohol, tobacco, certain firearm components, jtag smart card interfaces, gold coins...