Words matter and so do PsyOps and confirmation bias. Companies are savvy at marketing so they should tailor their apologies to trigger good will confirmation bias in their customers. Actually, according to pre-suasion, they should stage false flag events so help the public pick the right confirmation bias the second time.
Does anyone really believe in 'lone typists' when we live in a world where #Vault7 is likely on #S3?
Personally, I think we should all grow up and doubt all news accounts and company PR from any source, until cui bono and Analysis of Competing Hypotheses (ACH) in the Critical Thinking process they use in the IC and LE communities has been thoroughly engaged. Especially if the company has a contract for #SpookCloud.
I agree testing and automation are good. I think they need to go beyond this to formal verification, for something on this scale and reliability. NASA doesn't make these sorts of mistakes.
By the way - this is not just Amazon's problem now. We know the internet has a single point of failure. So does a lot of IoT.
(Specifically https://www.youtube.com/watch?v=6OalIW1yL-k#t=3m but it's worth watching the whole clip (or even the whole movie) if you haven't seen it before. It's from Terry Gilliam's "Brazil".)
>We know the internet has a single point of failure.
It has? I have yet to see the day where I can neither reach my email provider nor Google nor Hackernews. My local provider might screw up occasionally, or some number of of websites go unreachable for whatever reason. But I fail to come up with anything short of cutting multiple see cables that causes more than 50% of servers to be unreachable to more than 50% of users.
Amazon do formally verify AWS (they use TLA+), which is probably why this failure is a human error. Of course, you could expand the formal analysis of the system to include all possible operator interactions, but you'll need to draw the line at some point. NASA certainly makes human errors that result in catastrophic failures. The Challenger disaster was also a result of human error to a large degree[1]; to quote Wikipedia: "The Rogers Commission found NASA's organizational culture and decision-making processes had been key contributing factors to the accident, with the agency violating its own safety rules."
as long as you are going to experiment, why not use a smart contract to implement your license? If someone meets your reserve price, it goes open source earlier. You can have a salvage value close 3 years in the future if the terms of the Code Tontine are not met.
Isn't that what rot13 is for? A think a special compiler switch, along the lines of -Drot13, would work just fine for people who have special needs like that.
That's true now but not in all historical periods. In the original system, m. was an abbreviation for mille, and not a composable component of the numeral at all. In effect, it served as a comma does in English text today, to separate the thousands from the units -- both of which were encoded using the composable letter system we are now familiar with.
Later, of course, people assimilated the operation of the M to the other letters, esp. on the dates of printed books. However, if we are discussing manuscript practice in the 15th century, the medieval approach and not the modern approach to Roman numerals would likely be in play...
In any event, using mm. to represent mille mille (a thousand thousand, a million in modern parlance) would create no cognitive dissonance as it does today.
All pURLs are down. Internet meta just broke entirely unless you run your own purl resolver and change all the URLs.
http://purl.org/dc/elements/1.1/description
What is a pURL? https://en.wikipedia.org/wiki/Persistent_uniform_resource_lo...
It's an alternative to using DNS, essentially, woven into the XML standards among other things.