Arch doesn't use zram by default?
check the FAQ on chimeraOS here: https://chimera-linux.org/docs/faq#so-why-use-a-bsd-based-userland-anyway
Lovely write up!
can't you just trigger a script after some udev event? Your battery would be happg
One thing that hasn't been mentioned yet is interopability, that is, flatpak interacting with the rest of your system.
I'm not that familair with flatpak, but in my brief experience with the steam flatpak, I had trouble getting it to recognize my controllers. Steam installed through pacman (Arch's package manager) had no such issues, on the other hand. My hunch is that this has to with flatpaks being more isolated from the rest of your system.
Im pretty sure that's just some kind of permission issue, but it can be nice to not have to troubleshoot acces rights and the like. But this is obviously a double edged sword: more isolation may also mean more security, just at the cost of ease of interaction with other components.
One thing I really miss in adwaita is readline/emacs-style text navigation shortcuts everywhere.
Could the work on the global shortcut portal somehow help with that? Or is this already fully doable by way of extensions?
There's a compability layer, generally called pipewire-pulse. I think it's not a one-for-one copy, but it works great for desktop applications that expect pulse.
Some things that previously were pulseaudio modules, like rtp and raop (airplay), have been reimplemented as native pipewire modules, I believe.
More complicated setups I can't personally speak to, but since pipewire is also catered towards professional audio workflows (as opposed to just desktop audio), you should at least be able to replicate what you have now.
And, as others have already pointed out, pulseeffects has been long dead, and now lives on as easyeffects.
oops, didn't know about her politics
mpdevil! It's got a nice GTK4/Adwaita UI, integrates with mpd, and gets out of your way.
ITT: lots of angry boomers
view more: next ›
rien333
joined 2 years ago
They probably can not. Unless you've setup your router such that anyone can connect to an ssh instance running on your PC, and then also use a bad password. Public wifi + having something like ssh running + having a bad password.
Your PC probably doesn't satisfy these requirements (yay!), but some servers might.