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

That’s going to be a problem whatever solution you come up with, because of the federated nature of the lemmy system.

There’s no central authority to hand out usernames, so if two people sign up to different instances with the same username, any design which didn’t attach instance name to each username would fail. The only way around it would be for each instance to contact every other instance which exists, including the ones which haven’t federated yet, and negotiate ownership of the new username, and that’s just not possible

It’s a matter of perspective. To someone who’s job is to write the system which interprets ASM, ASM is high level

You declaring a debt isn’t meaningful because you don’t have legal authority to do so.

A licence statement is describing in what way you’re granting permission for something you do have the right to control, which makes it meaningful

Nah, we’re alright. I don’t think anyone has clearly defined the requirements of earth citizenship, we can assume it’s like Ireland who hand it out like candy

No it wouldn’t. Whoever touched it last is responsible for it, that’s entirely consistent with the metaphore

I’m pretty sure it means exactly what it says, but you lot are all misreading it.

I interpret it as “all rights, except the right to commit, are reserved” (which doesn’t mean you surrender the right to commit, but rather that it’s the only right you aren’t depriving everyone else of)

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)