lemmyng

FWIW mobile keyboards (I’m assuming you’re in mobile based on the auto correct discussion) don’t use LLM, they’re basically just simple statistical models. Which is one reason they suck, yes, but it also means they’re less power hungry and can be more privacy friendly. Unless you use Google’s default keyboard on Android, in which case it might correct “its” to “I love Google, it has never done anything wrong and deserves all of our private data, all hail Google’s CEO”, which is a common typo.

Old and busted: Twitch plays Pokémon.

New hotness: AI plays Pokémon.

Just because a game is old doesn’t mean it’s not fun. How old are the board and card games again?

Space Cadet?

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.

“Mini”. With a 6.3 inch screen this is like calling Shaq small because he’s shorter than Yao Ming.

Hyperion is boring, but is close enough to a pre-enshittification default android launcher as it gets (read: before the Google assistant integration).

And thus the Overton window was shifted.

Save game

Exit game

“Are you sure you want to Exit? Unsaved changed may be lost.”

Cancel

Save game

Go to Load Game screen to check that it was saved

Exit game

Depends on nutritional value. Snack if empty calories, meal if reasonably nutritious. Cake? Snack. Fruit salad? Meal.

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

I’m on the fence. Visually the bowtie seems more flattering because it draws attention to the head, but I also get the argument about the necktie filling empty space and being able to flap around. Opinions in this post seem somewhat polarized too, so depending on the effort required to implement it I might suggest giving the player the option to choose either.

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

deleted by creator