disablement

No accidents, no clients not paying, no disease or disablement? living in a safe, rich, area of the world?

There would also be the increase of all kind of death and disablement due to the breakdown of the medical system. So prob 1 month of all emergency cases wouldnt been treated.

The media attention alone will make Apple cave, and if not, a single week of app removal and disablement will make them.

Even if it motivated you to get a lot done, I'm not sure I want to live my life under the constant specter of fear of death or disablement. That doesn't sound very exciting, and doesn't lead one to take even the slightest risk.

This isn't just about death count, it's about a complete disablement of any sort of economy or infrastructure. We're basically fucked now.

The term “maintenance mode” specifically implies an orderly disablement. I expect anything it applies to to receive some sort of message as to what’s going on if you try to use it.

I will not be surprised if we see a temporary disablement of 'e-filing' before this gets fixed. Prescription fraud is generally laid on the insurers who will pass it on as premium increases.

Remote disablement of physical infrastructure, with due process recourse for misuse weeks, months, or years after-the-fact, truly terrifies me. This is basic health and safety stuff.

I wonder if the VT-d disablement is required for the rootkit to work. Ideally you'd have VT-d in macOS for virtual machines, but then again you also don't have Thunderbolt so maybe it's simply not complete enough to enable 'everything'.

Or, said the other way, enable the passengers to override the automatic disablement if they request and their position is determined to be passenger. there will still be hacks but if we could take care of x% of the problem then we would be far better off then today.

If this is truly just a random account disablement, then it would seem that Google needs to augment their customer support accessibility and procedures. If the author is/was somehow "competing" with Google on some level, or making anti-G remarks, I would be curious about such details.

But I've usually found that architectural solutions like canaries, automatic restarts, feature disablement, fallback codepaths, etc. are more effective at reducing errors per programmer-hour spent on them, and when you have those the reliability thresholds for the actual code you write can be much looser.

In this case, Wikileaks 'insurance' documents have in the past contained classified information; they are meant to function as insurance because the contents would embarrass or injure someone if revealed; revelation would be contingent on Wikileaks' dissolution or disablement; and it's reasonable to suppose that only a government could bring that about. Thus, your decision to host the files, even without knowledge of their content, involves an awareness of the strong possibility that they do contain classified information.

Maybe Krugman has a fair point if we were "merely" talking about severely underpaid workers making way too many hours[1], but it doesn't explain this: > The account of how Apple's factories substituted n-hexane, a neurotoxin with well-documented long term adverse health effects, for alcohol to wipe those shining screens clean, gaining a miniscule advantage in drying time but exposing workers to a lifetime of disablement [1] a fair point, which I will consider as soon as such a situation actually presents itself in reality. I bet it will be a factory that manufactures containers for thermodynamically closed systems, which are to be sold on a free market to rational agents.