Either it was a glitch on my side, or they really went from 6.2.5 back to 6.2.1 and from there to 6.3.

Anyway, nice update

So what’s the problem according to FF?

Combined with the news of an apparently massive first-day patch this seems like a game for patient gamers. Basically like the first 3.

Horse Armor

Hey, I remember that shit show.

18 years

Aaand I’m getting old… :/

The request from the other machines go through the firewall and are being redirected, the requests from the NAS are basically trying to connect to localhost, so no redirection here as the requests aren’t leaving the machine.

Docker Gitea to Docker Forgejo was basically using a different image and pointing it to the existing database. Not sure if and when both will be different enough for that to no longer work. But I also only use it as a docker compose storage repository. No idea about automation etc.

Oh well… Maybe I could finish the first part instead.

What do you mean, “proprietary”? Don’t they connect via Bluetooth?

I know, that’s why it always catches my eye when there’s “2 years” in there somewhere.

about two years

How convenient.

That was exactly the point. There are quite a number of cars with actual self-driving technology, where the driver is not responsible. Or if there is no driver.

Wait, you update productions systems without running a staging environment? Or even checking the update notes and your installed apps? Also no backups? What kind of business are you running over there?

If setting up TLS is too much work, better stay with a service. Signal is nice.

It really depends on if you need transcoding or not. If no, it doesn’t matter. If yes, check for integrated GPUs on both models and check that it will work as a transcoder for jellyfin.

Kavita works well for me.

Are you high?

Uh oh…

Same here, works fine.

The idea is that the router plugs in to your home internet and the server into the router. Between the two they get the server able to handle incoming requests so that you can host services on the box and address them from the broader Internet.

Why would I need a separate router for that? I’d need to configure the main router anyway.

Interestingly, I didn’t even have to touch it. Apparently it was still on my main page and Boost would simply crash after opening, until I hid the post in a web browser.