It is guaranteed, actually. US law imposes requirements on telecoms providers to support wire taps

No, basically. They would love to be able to do that, but it’s approximately impossible for the generative systems they’re using at the moment

No, I’m arguing that the extra complexity is something to avoid because it creates new attack surfaces, new opportunities for bugs, and is very unlikely to accurately deal with all of the edge cases.

Especially when you consider that the behaviour we have was established way before there even was a unicode standard which could have been applied, and when the alternative you want isn’t unambiguously better than what it does now.

“What is language” is a far more insightful question than you clearly intended, because our collective best answer to that question right now is the unicode standard, and even that’s not perfect. Making the very core of the filesystem have to deal with that is a can of worms which a competent engineer wouldn’t open without very good reason, and at best I’m seeing a weak and subjective reason here.

The reason, I suspect, is fundamentally because there’s no relationship between the uppercase and lowercase characters unless someone goes out of their way to create it. That requires that the filesystem contain knowledge of the alphabet, which might work if all you wanted was to handle ASCII in American English, but isn’t good for a system which needs to support the whole world.

In fact, the UNIX filesystem isn’t ASCII. It’s also not unicode. UNIX uses arbitrary byte strings, with special significance given to a very small number of bytes (just ‘/’ and ‘\0’, I think). That means people are free to label files in whatever way they like, and their terminals or other applications are free to render them in whatever way seems appropriate, without the filesystem having to understand unicode.

Adding case insensitivity would therefore actually be significant and unnecessary complexity to add to the filesystem drivers, and we’d probably take a big step backwards in support for other languages

Cuboids are prisms. Specially, they’re rectangular prisms

Why shouldn’t they? Nose and toes do rhyme.

It’s possible there’s some accent I can’t immediately think of where they don’t, but all of the accents which come to mind use the same sound in both cases

There’s no need to leave earth, just lift it into a medium earth orbit. There are literally thousands of kilometres in between low earth orbit (where there are lots of communications, spy, navigation and weather satellites) and geosynchronous (where there are lots of communications satellites), and outside of those two there’s virtually nothing there

In principle they could have pulled out slightly, if there’s jostling and tiny movements in skull then you’d expect them to work loose over time if they’re not securely anchored

The default is as long as it is because most people value not losing data, or avoiding corruption, or generally preserving the proper functioning of software on their machine, over 90 seconds during which they could simply walk away.

Especially when those 90 seconds only even come up when something isn’t right.

If you feel that strongly that you’d rather let something malfunction, then you’re entirely at liberty to change the configuration. You don’t have to accept the design decisions of the package maintainers if you really want to do something differently.

Also, if you’re that set against investigating why your system isn’t behaving the way you expect, then what the hell are you doing running arch? Half the point of that distro is that you get the bleeding edge of everything, and you’re expected to maintain your own damn system

The question you should be asking is what’s wrong with that job which is causing it to run for long enough that the timeout has to kill it.

Systemd isn’t the problem here, all it’s doing is making it easy to find out what process is slowing down your shutdown, and making sure it doesn’t stall forever

Just one padlock is enough, but you can use up to 6.

You need all the locks removed before it’ll open, so you don’t need to count on someone to carefully count everyone back in. You just make sure that each person uses their own lock

I find it makes my life easier, personally, because I can set up and tear down environments I’m playing with easily.

As for your user & permissions concern, are you aware that docker these days can be configured to map “root” in the container to a different user? Personally I prefer to use podman though, which doesn’t have that problem to begin with

Podman supports docker compose just fine. You have to run it as a service, so that it can expose a socket like docker does, but it supports doing exactly that

Because a container is only as isolated from the host as you want it to be.

Suppose you run a container and mount the entire filesystem into it. If that container is running as root, it can then read and write anything it likes (including password databases and /etc/sudo)