1,817 karma · joined June 9, 2009
As an individual who has lived in multiple countries in three continents, I dispute that “the care most people get is better than adequate”. Perhaps better than the world average, but certainly not better than in most first-world countries. And that’s not even counting the impact of delayed decisions and denied care, and the stress of dealing with the system overall.
And if you’re looking for more than anecdotes, there are plenty of studies that show that Americans have lower expected lifetimes than citizens of peer countries, despite much higher per-capita health care costs.
(I don’t mean to belittle your comment about universities which is factual and helpful. I’m just pointing out that US education system is just as fucked up as the US healthcare system the OP is talking about.)
But I can think of lots of examples where the response to an unfortunate, but very rare, incident can make us less safe overall. The response to rare vaccine side effects comes immediately to mind.
>>> Views of ‘cause’ limit the effectiveness of defenses against future events.
>>> Post-accident remedies for “human error” are usually predicated on obstructing activities that can “cause” accidents. These end-of-the-chain measures do little to reduce the likelihood of further accidents. In fact that likelihood of an identical accident is already extraordinarily low because the pattern of latent failures changes constantly. Instead of increasing safety, post-accident remedies usually increase the coupling and complexity of the system. This increases the potential number of latent failures and also makes the detection and blocking of accident trajectories more difficult.
Just one example: I was excited by the idea of having two apps on screen at the same time: there are two I like to look at side-by-side all the time. But one of them (an iPhone app) randomly decides to switch to landscape mode, making the layout unusable. More generally, the window controls keep getting activated unexpectedly by taps when I use full-screen apps like games, resulting in the window reverting to not-full-screen. So I guess I'll just have to turn that feature off until it's actually usable.
FWIW, I just used the Google app on iOS and got one ad (for artlist.io) before the midjourney.com link. A lot of people use Google this way to get to a named website, btw.
I’d be very interested to see the trendline of user-initiated search over time.
TypePad’s export process is awful: the output is a poorly formatted .txt file which is hard to parse reliably. The export process itself fails at least half the time. There’s no export process for images or style files. Automated crawl processes fail.
I LOL’ed at this part of the post:
>> If you have any questions, please refer to our Frequently Asked Questions page here.
The “here” link 404s.
* There was no record of a “Take Over Immediately” alert, despite approaching a T-intersection with a stationary vehicle in its path.
* Moore found logs showing Tesla systems were capable of issuing such warnings, but did not in this case.
By the way, if you’re used to 12h time, you can get a similar experience to that described in the article simply by setting your watch/phone to 24h time. After a while your brain just starts to recognize 15:00 and 3pm as the same thing, and there’s no explicit conversion required for you.
Sure, they faltered at Step 2, but how was this not the plan?
>>> The only hypothesis the committee could develop that provides a plausible but unprovable answer to all these questions and the observed socket failure pattern is that the socket zinc creep was unexpectedly accelerated in the Arecibo Telescope's uniquely powerful electromagnetic radiation environment. The Arecibo Telescope cables were suspended across the beam of "the most powerful radio transmitter on Earth." The other investigations failed to note several failure patterns and provided no plausible explanation for most of them. To answer these questions with empirical evidence instead of only the inferences that can be made from the existing data, a more comprehensive and widespread forensic analysis of "good" and "bad" socket workmanship and the low-current, long-term effect on zinc creep is required.
GitHub Copilot uses Claude 3.5 Sonnet hosted on Amazon Web Services. When using Claude 3.5 Sonnet, prompts and metadata are sent to Amazon's Bedrock service, which makes the following data commitments: Amazon Bedrock doesn't store or log your prompts and completions. Amazon Bedrock doesn't use your prompts and completions to train any AWS models and doesn't distribute them to third parties.
[1] https://docs.github.com/en/copilot/using-github-copilot/usin...
Given that this incident has now happened twice in the space of months (first on Linux, then on Windows), and that as stated in this very post the root cause analysis is not yet complete, I find that statement of “NO RISK” very hard to believe.
(It does look like the malicious ad is no longer being served, through.)
The correct solution is for a public information campaign to inform everyone never to click on any "Ad" link in any Google search ever. It's the only way to prevent our parents and grandparents from being phished, hijacked, or worse.