Podman not because of security but because of quadlets (systemd integration). Makes setting up and managing container services a breeze.

But check that it has all the features you need because it lags behind gitea in some aspects (like ci).

Podman quadlets have been a blessing. They basically let you manage containers as if they were simple services. You just plop a container unit file in /etc/containers/systemd/, daemon-reload and presto, you’ve got a service that other containers or services can depend on.

I’ve been in love with the concept of ansible since I discovered it almost a decade ago, but I still hate how verbose it is, and how cumbersome the yaml based DSL is. You can have a role that basically does the job of 3 lines of bash and it’ll need 3 yaml files in 4 directories.

About 3 years ago I wrote a big ansible playbook that would fully configure my home server, desktop and laptop from a minimal arch install. Then I used said playbook for my laptop and server.

I just got a new laptop and went to look at the playbook but realised it probably needs to be updated in a few places. I got feelings of dread thinking about reading all that yaml and updating it.

So instead I’m just gonna rewrite everything in simple python with a few helper functions. The few roles I rewrote are already so much cleaner and shorter. Should be way faster and more user friendly and maintainable.

I’ll keep ansible for actual deployments.

Yay, fan club.

I was just introducing someone to Rodney last night because some actor in a show we saw looked a bit like him. Then I wake up and see this here. Life sure has funny coincidences sometimes.

Shame he didn’t have a scandal on that stage. They would have stopped taking about it within the day.

I guess it’s too much to ask the richest company on the planet to keep a list of a few accounts indefinitely. I’m sure that database is a whole gigabyte sized and maintaining it requires a whole person to check in on it once in a while. Obviously they can only afford that level of effort for a year or two. And we’re only taking about removing access from millions of people to something they paid good money for, and also doing it because. Yeah, I’m with you on this one, totally not their fault.

All public companies are, it’s just what Boeing makes things that fall out of the sky if they mess up, so it’s more obvious.

Just have NAS A send a rocket with the data to NAS B.

If this was done by multiple people, I’m sure the person that designed this delivery mechanism is really annoyed with the person that made the sloppy payload, since that made it all get detected right away.

Because Bedrock runs on phones, tablets, consoles, and a host of other random crap

And it also removes Linux support. Typical Microsoft.

Then they’ll just identify you by the sound of the printer being audible from down the street.

Seems to me that a lot of the world’s problems start with “well, the managers think…” They all seem extremely bad at the whole managing thing, good thing we don’t overpay them or anything like that.

TIL there are Linux people that don’t use OpenWRT. I always assumed everyone in the Linux community used it. It’s great.

Works great with mt7621 based routers if anyone ends up looking for something compatible.

I use gnome for the most part. I have been checking out kde recently to see how the newer versions stack up (gave up on it during the 4.0 days). As you mention kde supports dpms changes on wayland because they have their own protocol extension for that.

That’s actually my biggest gripe with wayland - the huge amount of fragmentation it has caused. I’m pretty confident that almost all the missing features I talked about are possible on one or two of the compositors, but not all of them. And definitely not on the one I use. I’m sure once some pragmatism takes hold that all the issues will be ironed out, but my plan for now is to stick to X11 until that happens.

For me it’s a million little details that just don’t work. Stuff like positioning windows, removing decorations from a window, remapping buttons on a trackball, setting a graphics output to tvrgb, disabling a display via ssh and enabling it again, etc.

It’s not just about hardware compatibility. It has to be compatible with existing workflows, and it’s currently very limiting.

set -euo pipefail at the top of every script makes stuff a lot safer. Explanation here.

It’s like calling all fuel diesel.