Elvith Ma'for

AI does have excellent usecases. They just diminish to almost zero if you only look at LLMs

They even got ads for horse piss now?!

Just to add insult to injury for the cited statistic: they only count delayed trains. If a train has accumulated too much delay, they might stop it and make it turn around and it never completes its journey. This will count as a cancelled train instead of a delayed train and thus it is not counted as a part of that statistic… So the reality is even worse than you’d expect.

  /\
 /__\
 |__|
 |__|

Magic = making shit up
AI = magic sparkle ✨
Therefore
AI = making shit sparkle up ✨

Oooh, did someone look into a mirror while naked?

What exactly is NSFW mode? Asking for a friend…

I mean I get the idea of the forced restart and the general waiting time - assuming a scammer wants you to install a “side loaded” app, it will disconnect their call with you, of they’re calling you on that phone. Same for a waiting period that forces the scammer to either hang around on the phone with you for a long time or to call again some time in the future.

But 24h?

So… Now the pressure is gone? Or is it still there, but it’s not a drip anymore?

Argh, I meant + and then did a copy and paste error

It’s half AND half, not half TIMES half after all

half-and-half = 0.5 + 0.5 = 1
two half-and-half(s) = (0.5 + 0.5) × 2 = 1 × 2 = 2
three half-and-half(s) = (0.5 + 0.5) × 3 = 1 × 2 = 3
…

That’s basically my commit history for every repo where I need the pipeline to run to see if everything works.

To me sounds like either a neglected project

If it’s a depdency nested deep in the dependency graph, that doesn’t necessarily mean I abandoned my project. I might be using this dependency of a dependency in my project and don’t notice anything, if there is a precompiled version for the (Python/Linux/…) distribution I’m running on my machine, so I might not notice that. It might even be, that I keep my dependencies up to date, but someone up the chain isn’t. And maybe there isn’t really a viable alternative to that one dependency that pulls that package in.

An example: If Im ever going to sell my Nintendo Switch (1), I’m absolutely going to include the model number. The reason: It’s a launch day Switch. While this means that it is the oldest model and also the battery might have more wear than a newer model, it also suffers from an unpatchable hardware bug that allows you to hack the system (and run homebrew, pirated games, modded games,…).

Police in Burgenland said in a statement that a sample from one of the 190g (7oz) jars of carrots and potatoes baby food reported by a customer had tested positive for rat poison

[…]

The police statement said the affected jars had a sticker with a red circle on the bottom […]

Now… Was it one or were there several?

With an old Kindle, it was trivially easy to rip Kindle books to retail-quality epubs.

Heh, yes. The encryption key for their old DRM was derivated from the Kindle’s serial number. Wanted to crack your library? Go to the webpage, download them all there (yes, that’s now blocked, too) open them all in calibre and use a plugin to deactivate the DRM (trivially to find back then). Enter your serial number and you’ve freed your whole library.

There’s also a relevant xkcd for that.

There are some projects, that do not offer latest or a general tag to pin a major version. So you might need to account for that.

Also since a few years ago you can specify pull_policy: always in the docker-compose.yaml to always pull the images on start. That should at least auto update the containers on a server reboot after OS/Kernel updates.

Unless you forgot AutoUpdate=registry in the .container file for half of them, like I did.

But yeah, I switched to Podman over a year ago and I’m not looking back.

How else would I be able to complain?