That's what containers are for. Fucking up the container won't fuck up the host. That was the best decision in self hosting I've done. Even that one virtual machine feels weird and uncomfortably legacy now but it needs to interact with hardware in a certain way that just won't fully work with docker.
Lichtblitz
Fascinating. That's much more than I expected. Thanks for taking the time.
The image doesn't look like a photo. The meme is about porn. Digital images can contain large areas of repeating patterns (uniform color areas for example) that can be compressed losslessly pretty well. Even slight noise from an image sensor can block that kind of compression.
You're right. png can be lossy but that's uncommon in the wild.
bmp should not compress more than other media files. jpeg, png, etc. can compress so much because they are lossy
Python doesn't have to. Windows supports both out of the box. Has been for many, many years
No. Because the python version of the host and the target server must loosely match up. Otherwise you get some cryptic error messages in some unexpected modules. Red Hat's solution: just manage RHEL 9 targets from RHEL9 hosts and RHEL8 from RHEL8 hosts. There is no official way to align python versions across that major.
IBM owns Red Hat.
My (self-hosted) cloud storage is larger than the disk drive on my laptop. On demand sync is important to me. I really, really hope Linux will catch up to Windows in that regard.
Currently we have an experimental VFS feature on all platforms that is using some suffix appended to files when they are virtual empty placeholders. https://github.com/nextcloud/desktop/issues/3668
Yeah, no thanks. It's a very hacky work-around and breaks the moment you use an application that tries to access the files directly.
On topic YouTube video by a rather popular German Comedian:
Germany's Far-Right Comeback | NYT Opinion