Some older consoles have very negligible size libraries in modern day terms, and who knows what sources of ROMs will be taken down by lawsuits in the next few decades. I feel like there is some sense in making a complete archive of a systems game library, but for my personal use I usually just download / dump / rip what I need specifically.

Whatever file format I use them in is also how I back them up, I backup my entire desktop’s and laptop’s data to an external hard drive and an online service provider. I’m sure a compressed format would be more space efficient but that would take much more time given my use case.

In the case of my laptop it runs Linux and the filesystem I use supports “transparent compression” (almost all contents of the drive are compressed with zstd), so I’m guessing any of the ROMs on there will have already been compressed as nuch as they can (but I’m not knowledgeable enough on the file format specs)

I have a few shortlisted

My parent’s 2010 Ram 1500, the interior is rather comfy but the reliability is just not there. At 100k km the engine blew up, apparently this is still an issue with the current ones as the 5.7L V8 still has the same flaw allowing for some components to drop into the cylinder. There’s also been random electrical components that have died relatively fast, and whatever metal was used rusted exponentially even with rust proofing being applied twice a year. It had more rust than their 2011 Toyota Highlander that had greater than 300k km

I also just hated when I had to drive it downtown, but I can’t exactly blame the vehicle for that.

2011 Toyota highlander, it went through 3 transmissions, 5 rear wiper motors, and it was about to go on to its 4th transmission when they sold it. The 3rd one didn’t even last much more than a year.

2006 Rav 4 (V6), this car also went through 2 transmissions, and then had to have the entire steering column replaced by year 2

~2016 Ford Fusion, this was a rental car for when my Civic was being repaired after an accident and my god was it awful. It handled like a massive boat despite being a medium sized car and the transmission felt significantly less responsive than even the CVT in the honda. The seats also sucked but i think that was how the rental company cleaned them, they made this awful noise every time you sat in them and looked and felt like a “casting couch” with several generations of children dried up in them…

Honorary Mention: my friends Nissan Versa, seemingly unreliable and falling apart but it refuses to ever give up. That thing will survive nuclear winter, and will remind you with every pothole that its existence is torture.

I understand why they wouldn’t want to suddenly change the branding of existing projects though.

I’m not sure if I agree, I feel like the long term damage of keeping the names is greater than changing them now to Fedora Plasma Atomic (Formerly Kinoite) / Fedora Atomic Workstation (Formerly Silverblue). Leaving them as is, is just going to create more confusion in the future to new users who won’t immediately understand why the naming convention is different for the other spins and will create more confusion for documentation / support threads online.

I feel that I am 50:50 on it, immutable at least conveyed more information about what it is while Atomic feels a lot more “buzz-word-y” and does not convey as well what it means. Regardless, I’d say the bigger issue is keeping the old Silverblue & Kinoite names, they really should change them even if it means having a ~2 year period of having “Formerly Silverblue / Kinoite”.

Thank you for the very thorough reply! For god knows what reason I get this error: error: app/org.mozilla.firefox/x86_64/stable not installed when running the xdg-open firefox-reader command, yet manually running flatpak run --user org.mozilla.firefox about:reader?url=https://example.com works just fine. I’ll have to troubleshoot it when I have a bit more time ;p

Thanks again for your very thorough write up and the linked articles. Have a good day :)

Update: It seems like on my system, the --user flag was the issue, removing it made the script function. I am using Fedora Kinoite (Immutable version of KDE Plasma), so perhaps it is just a difference in how flatpak is configured between distros? I’ll have to read into it more later.

I’ll keep my answer focused on KDE Connect as I no longer use a TWM. You can most definitely use KDE Connect in non-Plasma environments. For non-Plasma (and non-Gnome ^* ) environments you can just install the kdeconnectd package. Then, to start the KDE Connect daemon manually, execute /usr/lib/kdeconnectd. You can schedule this to autostart as a systemd unit, or in the config for your TWM (I know in sway/i3 you could start it, I’m assuming it is similar for many other options)

If you use a firewall, you need to open UDP and TCP ports 1714 through 1764. If you use firewalld specifically, there’s an option to enable KDE Connect rather than manually specifying it. This also let’s you have it only work on private networks and not public if you so chose.

See Arch wiki for more details

*For gnome I would recommend using gs-connect even if you have a tiling extension

£ KDE-Connect: does that work on TWMs? Is there a good implementation? Can I use GSConnect elsewhere too?