An overarching principle of security is that of minimum privilege: everything (every process, every person) should have the minimum privileges it needs to do what it does, and where possible, that privilege should be explicitly granted temporarily and then dropped.

This means that any issue: a security breach or a mistake can’t access or break anything except whatever the component or person who had the issue could access or break, and that that access is minimal.

Suppose that you hit a page which exploits the https://www.hkcert.org/security-bulletin/mozilla-firefox-remote-code-execution-vulnerability_20230913 vulnerability in Firefox, or one like it, allowing remote code execution. If Firefox is running as root, the remote attacker now completely controls that machine. If you have SSH keys to other servers on there, they are all compromised. Your personal data could be encrypted for ransom. Anything that server manages, such as a TV or smart home equipment, could be manipulated arbitrarily, and possibly destroyed.

The same is true for any piece of software you use, because this is a general principle. Most distributions I believe don’t let you ssh in as root for that reason.

In short: don’t log in to anything as root; log in as a regular user and use sudo to temporarily perform administrator actions.

P.S. your description of the situation shows you don’t know the nature of vulnerabilities and security - if you’re running servers then this is something you should learn more about in short order.

you could instead do:

dcl() { docker container ls -aq -f name="$1" }

in bashrc or wherever you’re setting this up.

Why create the function _dcl()?

Must be time for a new Linux audio system. The pipewire-pulseaudio-ALSA stack of compatibility layers is old hat already.

I remember looking into the situation with non-destructive editing about… 20 years ago. I wonder how long it’s been a desired feature!

I don’t think a good response to " breaks " is to say "yes, because was designed to work with and hasn’t been updated to use ". Part of the task of replacing something old - onerous though it be - is to provide a smooth route to support old programs and functionality.

Wayland deliberately broke everything, but then was rolled out prematurely at least on some distros, before giving the vast X ecosystem enough time (which was guaranteed to be a long time, due to how large and entrenched it was) to update. Besides which, the “OUTDATED” post has an awful lot of things you acknowledge are still issues!

Do you mean you want separate sets of workspaces on each monitor and to be able to switch through them independently? Just having “workspace 1 on monitor 1 and workspace 2 on monitor 2” sounds no different than the default behaviour with no extra workspaces.

Thinkpad X13 with a Ryzen 6850U.

I actually need to send it in for repair - I think the GPU is fucked as I get irregular crashes where the screen(s) all go black, audio keeps playing but input is broken, and other weird things, like sometimes an external monitor flickers and shifts so the left third is actually shown on the right hand side of the screen…

Rules around preventing a hostile work environment don’t place an obligation on anyone to prevent it at all costs. It means that if an employee or - more relevantly here - a customer - is being hostile, then the workplace needs to make sure the employee or customer stops. But if you work in a call centre cold calling people, your company isn’t going to get fined if you get an earful of abuse. (They might get fined for cold-calling depending on specifics :P) Same here.

I get 8-10 on my AMD laptop, but yeah it’s nothing like Apple unfortunately.