Three people, working independently, made errors in programming and website updates which nearly bankrupted United Airlines when the errors came together on September 8, 2008. "Shares fell to about $3 from more than $12 in less than an hour, wiping more than $1 billion in value before trading was halted.".
When the market first opened that Monday, United Airlines was trading at over $12 a share. The public summary of the events state that Chicago Tribune re-indexed their archives, resulting in a six-year-old story about United Airlines bankruptcy to be re-posted on the Web site of The South Florida Sun-Sentinel without a date. Google picked up the "new" article, saw the missing date, and inserted the current date of 9/8/2008. That article was picked up by a research firm, Income Securities Advisers, which then posted a link to it on a page on Bloomberg News, which sent a news alert based on the old article. The news alert triggered automated trading systems to issue sell orders. Nasdaq finally ordered a halt in trading the stock at 11:08 a.m, but the damage had been done, United Airlines Stock had lost 75% of it's value.
I was hired as a firewall admin at an online trading company, then quickly discovered the director of IT was insane, but kept management happy because he made his numbers by keeping his team constantly understaffed; I was told to work on not just servers, but installing Sun servers in racks, running cable, and fixing just about anything plugged into the network.
I made the mistake of showing competence in networking, so was asked to "expand my role" (new title, same salary), and start working on the switches themselves, including executing an "upgrade" to stacked HP ProCurve switches with VLANs (replacing a hodge-podge of random manufacturer switches). The actual upgrade went fine, basic testing (ping) showed everything stable, but as soon as trading opened the next day, everything went to hell, performance dropped through the floor and customers started calling in about trades timing out. Long story short, turned out that Solaris HME cards were unable to negotiate properly with ProCurve switches, half the machines were dropping packets due to duplex mismatches. There's a reason people call the Sun interface cards "Happy Meal Ethernet"
Cost the company approximately $180,000 in direct and customer exodus losses, and was likely a factor in their eventual collapse. I wasn't fired, but management never trusted me again so I saw the writing on the wall, and quit to do consulting work at a (also doomed) dot-com online supermarket.
On the upside, I was able to make thousands in consulting income from installing those same "lock speed to 100 and duplex to full" Solaris scripts on servers for various customers who also had performance issues plugging in Sun servers to cheap switches.
Yes, but aren't the steam generators closed loop? If you keep blowing out steam, you need to replenish water. That water must be stored on board or extracted from the sea water. I doubt that it is a good idea to use sea water in the generator; higher corrosion and all that jazz. The advantage of an electric system, is no consumables wasted, save fuel for the initial generation, which you would have used anyway.
Nuclear aircraft carriers have large scale desalination (distillation, aka "flash evaporator") plants, some capable of producing 400K gallons of distilled water each day, in excess of shipboard daily water needs.
How will Amazon handle the theft problem? Why just steal a package of unknown value when you can stuff the drone into a steel box and get a pile of expensive parts along with whatever bonus you find in the package being delivered.
Will Amazon be forced to redline neighborhoods that have a high attrition rate?
I just read the entire article and the author forgot one other solution: the British solution Instead of putting the burden on app developers to include backdoors, or on Google to block apps that don't, put the burden on end users to turn over their keys to police when asked. I'm not saying I like this solution, but it is a solution the author of the article didn't consider. If you make the sentence for non-cooperation long enough, it doesn't really matter if the police find what they're looking for: they can just lock you up for not handing over the keys.
In the USA, this would likely require a constitutional amendment, it is widely held that the Fifth Amendment "Right Against Self-Incrimination" protects the right not to divulge an encryption key.
Americans work longer hours and take fewer vacations than most others in the developed world.
We shoot each other more often as well.
With the possible exception of Postal workers (sorry, stereotyping) people who work 60-hour weeks and take no vacations are unlikely to be the ones doing the shooting -- they are doing the work of two people, and that other guy, the guy whose job the over-achiever has eliminated, is more likely to one with time to spare to go out murdering.
As productivity increases, companies can get more done with fewer workers. Good for profit margins, not so good for unemployment rates.
This seems like an odd bug to have happen, how bad were the effects? Just 'weaker' randomness, or without randomdev_init_reader do the random routines just return the same series of pseudorandom digits every time?
There is only one way you can EVER be compelled to testify and actually ANSWER their questions (you aren't allowed to lie, but you can refuse to answer, the "right to remain silent" applies to your TRIAL as well which is why defendants can't be compelled to testify) and that is you have to be given IMMUNITY. If the prosecution gives your testimony immunity you cannot be prosecuted for what you say (unless you commit perjury and lie).
One undecided facet is whether compelling somebody to "testify" by providing their encryption key or by requiring them to unlock an encrypted device, also gives them immunity for the evidence revealed in the contents.
One legal theory is that a person may be compelled to decrypt (e.g. by sitting them in front of a laptop with a copy of their PGP disk volume and saying "unlock this or go to jail"), and the only immunity required is immunity for prosecution due to the fact that they knew the key (e.g. a conspiracy charge), without granting immunity for evidence found in the cleartext of data in encrypted storage. I disagree, but can see that approach passing constitutional muster
The ISY (upgrade to the 994i if you haven't already) has a very nice and fully documented REST interface, included in the base license. There is an optional module enabling it to make calls out to remote network resources and also host web pages internally on the microSD storage card.
You don't need to use their proprietary programming interface. The same PLC or "PLM" (PowerLinc Modem) that the ISY uses can be accessed directly as a serial device if you want to work with Insteon devices at a low level from your own hardware, such as a Raspberry Pi.
The worst part about Insteon devices is that they have x10 support which can't be disabled. It results in devices switching on and off randomly.
This may have been true when Insteon was first introduced in 2005, but has not been the case for at least the past 5 years. No new Insteon devices come with X10 addresses programmed in by default, and Insteon is almost entirely immune to accidentally responding to noise on the power line by switching on and off randomly.
Insteon support site now states "Please note that most new Insteon devices no longer support X10 communication.".
In general, Insteon is not a particularly secure protocol, and is vulnerable to sniffing and replay attacks. If you need devices with stronger security, consider more recent home automation protocols such as Z-Wave.