The russian soldiers are in an awful predicament in this war. But they are still the aggressors and Ukraine has the right (obligation even, seeing what Russia tends to do to civilian population it conquers) to defend itself against them…and as awful as these weapons are, they have not been used in an illegal way here according to international law (something that Russia doesn’t give a flying fuck about, btw.).
Personally, I don’t see a moral issue here though I of course would prefer if noone had to die of which only happens in the case of Putin withdrawing his troops right now.

Couldn’t it be possible to set a script that restarts jitsi as that user’s login shell?

Play on Linux has been succeeded by Lutris or Bottles. I’ve tried both and personally I have fewer issues with Lutris but Bottles UI is a lot more intuitive. So I’d suggest trying Bottles first and if you run into issues use Lutris.

The clear cut of state data, pillar data and formulae feels more intuitive to me than Ansible’s playbook organization.

I use SaltStack to automate my servers. Just feels better than Ansible to me.
For my PC and laptop I don’t do anything, I haven’t hopped distribution since I started using Tumbleweed a few years ago.

The main distribution we use has it like that by default and our (admittedly rudimentary) benchmarks haven’t shown much of a performance difference versus ext4 so we kept to the default.

We use btrfs for the / partition and xfs for any data partitions. Has served us well, the snapshot feature saves us some valuable time when an update goes awry.

That 0.18mb accumulates quickly on the server’s side if you have 10000 people trying to access that image at the same time. And there are millions it not billions of images on the net. Just because we have the resources doesn’t mean we should squander them…that’s how you end up with chat apps taking multiple gigabytes of RAM.

I agree that the code is probably poor but I doubt it was a conscious decision to crash the OS.

The code is probably just:

1. Load config data
2. Do something with data

And 2 fails unexpectedly because the data is garbage and wasn’t checked if it’s valid.

Problem is that software cannot deal with unexpected situations like a human brain can. Computers do exactly what a programmer tells it to do, nothing more nothing less. So if a situation arises that the programmer hasn’t written code for, then there will be a crash.

I fixed a bug in an open source project we use and got into trouble for it :|

Which apparently needs an account just to use it and a subscription to use it well. Don’t think something like that can be a lord and saviour over LaTeX.

Most Video Games work on Linux these days.

Anti-Cheat software is usually still a problem though due to their invasiveness that cannot be handled easily.

This saddens me. The comments of the animes I watched usually had some interesting trivia or background information that I had missed.

Same thing that happened at Boeing.

Quassel, self-hosted.

I really wish we’d have chosen a term that does not include “sex” because it leads to a distorted view such as yours that it must be sexual. It’s in the name after all, right?
But heterosexuality has been promoted to kids for ages now! Children’s shows include married couples for example (husband + wife) or the main character goes into a relationship with a character of the opposite gender. So why does the same thing suddenly become “grooming” and “inappropriate” when it’s husband + husband or wife + wife?

Also, covering homosexuality in school does not equate to having “kids choose their sexuality”. Not to mention that it’s not a choice anyway.

Don’t think it would be that easy. What Yast does is creating a middle layer between the actual config files and the user. You can look at it, most (if not all) of it is stored in /etc/sysconfig. Yast generates the actual config files out of what is stored there. This can be a headache because editing the config files directly will sometimes lead to them just being overwritten bei Yast again.
This is probably the reason why other distros don’t even want to adopt Yast, it would have to fundamentally change how it interacts with the config files.
And the cool new thing is Cockpit anyway, even though it can do only a fraction of what Yast can last time I checked…

No, the equivalent would be a kernel panic that the other user had linked. This is a situation where the RAM is fully used and a program’s request for memory cannot be fulfilled. This is still a very bad situation because pretty much everything will grind to a halt. The Linux kernel thus makes a decision to kill a process (or multiple) until enough RAM is available again. Usually it kills the process with the most used RAM, but there’s methods to influence the decision.

I don’t think many docker images out there will have keepassxc installed though.