From my point of view, nothing else but NetworkManager makes sense to ship by default for a distribution aimed at desktop use. So I fully understand distributions doing this. My point was rather that this is not related to any particular WM / DE.
What’s broken? I just added a vpnc connection on my machine (granted can’t test it since I have nothing to connect to) but there was a vpnc connection profile until I deleted it.
Neither GNOME nor Plasma depend on NetworkManager, do they? Plasma will happily show information about connections managed by something else than NetworkManager, but won’t be able to manage them itself. But desktop distributions will most likely ship it as it covers basically all use cases.
I use both depending on the device. My desktop at home and all servers use systemd-networkd and I’m very happy with it. Right now, I’m on vacation and NetworkManager comes in very helpful with the ability to quickly manage networks as a normal user with a graphical user interface.
It’s a good question what I really want. I’m very satisfied with my current system (NixOS) but in the end it’s still Linux and stuff like the 9P filesystem just intrigues me. So it’s not like I’d need to switch or anything. But a playground to apply the concepts to some problems would be nice. Maybe I’ll try 9front some day and see what I can do with it
I’m also looking forward to Bcachefs, but rather for storage of large amounts of data. Just hoping the multi device feature works as well as advertised
Nothing, the licenses are for content providers and equipment manufacturers, obviously in the end you pay the license when purchasing the goods but the amount is small.
I think your workflow is not optimal. Are you using software like Radarr and Sonarr? They do the renaming for you and come with Kodi integration. Or is this not feasible?
I’m daily driving Firefox with Wayland on KDE Plasma since years, not on Xwayland, and can’t remember it not working well. This on two different distributions (Arch and NixOS). Not saying this is your fault but your experience is not representative for everyone
yEnc isn’t a cipher, but rather an encoding for mapping binary to text, similar to base64 (but much more effective). So this denotes yEncc encoding.
The files you’re seeing are PAR2 files, which are used for repairing. They’re useless without the base file. The file in your example contains 32 recovery blocks. That means if your base file has 32 or less damaged blocks, this parity file can repair it.
Usually, you’d download all files belonging together in a single download and let your downloader do the rest. This is normally done by loading an NZB file that you either get from a Usenet search engine or an indexer.