There seems to be a global option to reduce opacity, too. Anyway, I agree, contrast and readability is a problem with ideas like that.
Now, Phosh and Gnome look even better and more usable in comparison. But without Android apps or open APIs for all major services (to build native apps), postmarketOS can never be my daily driver for now.
At least, iOS changes like that increase the chance that the postmarketOS ecosystem will catch up. I whish I had the time or ressources to contribute in any fashion.
I have it working with just one LUKS volume. The tricky part is, that the UUIDs of the decrypted and encrypted device differ. I would have to look at my setup to be sure (it has been more than a year I set this up and I am currently not on my computer).
I am using gentoo-sources-6.12 . Idk, how mainline that is. It is pretty upstream with some Gentoo patches, I guess.
To increase the responsiveness of the system I changed the default setting of the scheduler to prioritize user input over system background processes (I don't remember the exact config name in the kernel). Other than that, I compiled it very close to Gentoo handbook recommendations: selecting only what I need and carefully choose between compiling drivers and features as a module or builtin.
I have gone from borgbackup to rdiff-backup to reduce complexity and dependencies. rdiff-backup's incremental strategy needs more space than deduplication from borgbackup, but you don't need fuse and borg itself to restore your latest backup.
With rdiff-backup you can just use cp -a to restore all your files. Only if you need a file you deleted ages ago, you need it.
I relied on borgbackup for a long time, never had an incident. But then I wanted to try the new replication borg2 feature and almost lost my original borg1 repo. With rdiff-backup you can just rsync the repo to another drive and have two copies of your offline offsite redundant backup. Encryption is a non-issue, you can run it on top of every other filesystem and LUKS or over SSH.
Granted, I just switched to rdiff-backup, but I am loving the simplicity of it already.
Unfortunately I don't have the same setup: I use the xboxdrv kernel module to use the PS5 controller for Steam games without native PS5 controller support. I deactivated Steam input for this game (Elite Dangerous, btw.).
I connect (USB) the controller before starting Steam. After connection I immediatly unload the hid_playstation module and start xboxdrv as root (I needed to create a custom mapping for it). Only after that I start Steam and can use the PS5 controller flawlessly in-game.
You might ask, why I am using a PS5 controller instead of an xbox controller. It's all about ergonomics. The PS5 controller is simply better for me.
I don't now which of ProcessColorModel or ColorConversionStrategy is the important one. I kept both and did not bother to try to omit one of them. -dPDFSETTINGS=/prepress makes sure that embedded bitmaps are in 300dpi and I think -f prevents Ghostscript staying in interactive mode after all pages have been finished.
Oh "Vergissmeinnicht", beautiful ("vergiss mich nicht", german for "don't forget me")