Shinji_Ikari

Typically volume of a track is chosen by the producer/person mixing. You could theoretically get an average volume and scale the tracks gain. This could have the effect of compressing or chopping parts of the song that are purposefully loud while the rest of the song is purposefully quiet.

I think it isn't done in order to maintain the intention of how the track was mixed. Typically people won't have playlists of quiet classical mixed with maxed out edm so a general rule is hard to predict and the authors of the music player just leave it as is.

Look into the cd loudness wars of the 90s where record companies were mixing their tracks louder and louder to compete, which produced notoriously terrible album mixes.

there's this awful venn diagram of circles with no overlap, where you cant get a smallish phone that gets updates. Even asking for it to be well made is a pipe dream.

Add onto the desire for an unlockable bootloader and your only options are the phones designed to be thrown into a river after the job is complete.

I wish those unihertz devices were serious whatsoever. They ship on old android versions and get maybe one update in their life cycle.

Android is such a clusterfuck of an OS too. kernel/driver space is an absolute mess so every OEM has to basically ship their own kernel. Qualcomm is the devil and hides everything behind NDA's so you can't really write an open OS from the ground up on any hardware that can do any real processing.

I just think its good.

The way I see it, you can have an OS that breaks less often and is hard to fix, or an OS that breaks a little more often that is easy to fix. I choose the latter. 99/100 times, when something breaks with an update, it's on the front page of archlinux.org with a fix.

The problems I've faced with other distros or windows is the solution is often "reinstall, lol", which is like a 3 hour session of nails on a chalkboard for me.

twist: Cotton got robot legs, is off somewhere doing something absolutely awful

I'm gonna comment and say that's the point.

You start out with bare minimum and install what you need. As you go you generally have an idea of what is and isn't on your system. It's not as annoying as Gentoo with all source compiling, not as anal as nix.

If something breaks, you go to ArchLinux.org and 95% of the time it's mentioned on the front page so you follow the instructions and move on. It's a very transparent distro, little drama to follow unlike Ubuntu/canonical or fedora/redhat.

It used to be harder to install and which gave some street cred, but they simplified it a bit which is nice.

The Stans give an unbalanced look at arch. I use arch because I want the latest packages, I don't want to segment my packages between my repos and tarballs when there's a game stopping missing feature on a package pinned to a 2yo version. I don't want to learn a whole scripting language to carefully craft my OS like nix either. I want a current OS that's easy to fix and easy to install packages so I can go back to what I was doing.

I had only used kde once before like 7 years ago and I wasn't a huge fan. I wanted to try it again and I honestly really like it over gnome. I usually go tiling but felt lazy with a new laptop. The trackpad gestures are really solid.

nmcli is quite nice actually. My only real issue with NM is keeping track of what it's doing behind the scenes.

So I want and have ip forwarding, and I only want to make a firewall whitelist between two of the interfaces.

I've uninstalled iptables, nftables isn't running, NM has the firewall backend disabled, and ip forwarding is on.

This should result in traffic moving between the interfaces, yet traffic is moving between two of the interfaces, and blocked between two of the interfaces. It just doesn't make sense.

Thanks for the suggestion, but I'm using NM for managing the AP and managed connections, not so much the bare connecting to wifi things.

The only real alternative to NM in this situation is a handful of delicate config files for iwconfig and dnsmasq.

A lot of software wont be distributed with a PPA to add.

Additionally, debs are useful for offline installations, with apt you're able to recursively download a package and all of it's dependencies as deb files, then transfer those over to the offline machine and install in bulk.

That being said I've never had great luck with the software center, it's always felt broken. I'll typically just dpkg -I <pkg>.

I think I first installed linux some time around 2009. I'm only just now starting to contribute to libraries, unrelated to linux. Its such a cool feeling growing along side the open source movement.

Polonium

Hm I'm not sure if that'd really give me what I'm looking for. I know its certainly possible to configure KDE and Polonium to get me 90% there but I think I'd rather just have a normal floating setup I can switch to if need be. I'd need to remap a significant amount of keyboard shortcuts that would stop making sense in the context of a full floating DE.

I really just want a very fast app launcher like dmenu, dynamic tiling, and monitor independent workspaces. I have a particular setup using certain alpha keys for my workspace.

I never really enjoyed the experience of tacking things onto an existing DE and having to mess with UI configuration. I've been really loving XMonad for a few setups and my ideal wm would be something that's extremely low power and low fluff. Even if I only eek out 10% more battery life, breaking the 10hr mark is more valuable to me than most bells and whistles.

I'm just really lazy. I could load up my xmonad setup in 20 minutes but I wanted to see the state of wayland and that requires learning a new wm's configuration quirks.