lemmyng

The prompt says “can boot”, not “is usable with”. If it gets to the kernel and then hangs that still counts.

Robert Miles would rank higher anyway.

They’re basically modern privateers - acting on behest of their leader nations, but with public deniability. Every once in a while I wonder what it would take for a Nemo-type character to show up, commandeer a submarine, and start stalking/hunting them.

Other kinds of severe weather are predictable, whereas there’s a big difference between “this pattern could develop into a tornado over the next half hour, batten down the hatches” and “A TORNADO HAS TOUCHED DOWN NEAR YOU, GET TO A SHELTER WITHIN THE NEXT MINUTE OR YOU’LL DIE!”

Icewind Dale did the same with Baldur’s Gate. Not just the UI, they blatantly reused a lot of the assets too!

I haven’t read the Tiny Pointers article yet, but the OP article implies that the new hash tables may rely on them. If so, then the blocker could be the introduction (or lack thereof) of tiny pointers in programming languages.

Using LLM for format conversion is like taking a picture of an electronic document, taking the card out of the camera and plugging it into a computer, printing the screenshots, taking those prints to a scanner with OCR, turning the result into an audio recording, and then dictating it too an army of 3 million monkeys with typewriters.

And thus the Overton window was shifted.

Conspiracy theorists don’t care that there’s a conspiracy. They only care whether they’re in on it.

Keychron keyboards are solid and maintainable, and available in Canada. Pick a model that supports swapping switches, and start with brown switches perhaps - they’re on the more quiet end of the spectrum, but common so you won’t break the bank. Then over time you can customize it as your budget allows - different switches if browns are not the right fit for you, keycaps of your preferred colour, etc.

To be even more pedantic, OP has not provided sufficient information to infer the series. No specific order is defined, so 0001 could be just as likely as 8259.

Renders in Summit, but I turned that off because any post title starting with # is rendered as h1.

See the other threads. I Posted the comment once, but something (either client or server) kept posting it. It could have been a temporary misconfiguration (happened at least once before), a bug in the server code, or a combination of unreliable network and my client retrying.

I didn’t, but now I’m paranoid that whatever caused the comment to be sent multiple times is still going on 😅

I know you joke, but likely not far from the truth. I was talking about misleading sensors, and this is an example of that - either my client didn’t get a response from the server indicating that the comment was received and retried, or my server didn’t get a response on OP’s server. Either way miscommunication happened, and the result (repeated comments, and from what I can see received at different times too) is much worse than the desired result (one comment entry only).

Very odd, I swear I wrote the post only once. I was having slowness loading the page - maybe there was a problem with my client not being able to get a response from the server and retrying, or the server processing the post multiple times (timestsamps are odd too)? Kind of serendipitous though - one system not getting the data it expects, and defaulting to a behaviour that is unintended.

This is highly unusual.

Depends on the field you’re in. In IT cascading failures are common.

My gut tells me that there was also a sensor failure and that the pilots were operating on erroneous information, which caused them to take actions that ended up compounding the problem.

deleted by creator

deleted by creator