"I can't stop the heterocyclic declination!" (TNG: "Samaritan Snare")

For a while I daily drove a Purism Librem 14 with Debian's fully free kernel, and installed as few non-free packages as possible, including firmware blobs (which I didn't install any of until I decided I needed Bluetooth). My experience with gaming was generally fine.

With linux-libre you really have to buy your hardware specifically with support in mind. You're limited to Intel and non-bleeding-edge AMD graphics cards, a very small range of wifi cards, and no Bluetooth. Otherwise, video games should work as well as they would on any other computers with the same specs. Especially if you're also limiting yourself to games with free engines - I'm not aware of a single libre game that demands more than a modern Intel integrated graphics card can provide, even on high settings.

I've never used these, but I've come across them while scrolling through F-Droid and they seem to fit this use case:

Kotatsu
Kinoko

This article seems to assume that advertisers don't want our identifying information, and are clamoring for an alternative to tracking that lets them measure ad performance anonymously, which is just not true. Being able to uniquely identify users and target them is a feature, and getting more data points from the browser just helps add to their profiles.

Now I'm (tentatively) excited to see how they'll outdo a season with a novel gimmick in each and every episode, including a musical and a crossover with a parody show, in terms of gimmicky weirdness.

"Klingon ambient" would be a good concept for an album.

1. I believe there is still an issue with Windows deleting Linux bootloaders during some updates. You'll be fine if you install Linux on a separate disk, and even if you dual-boot on one disk and the bootloader gets deleted, there are ways to recover it. You don't strictly need to have separate data and OS partitions, and I've gone back and forth on whether I prefer it - it makes distro hopping and disk encryption easier, at the cost of potentially inefficient use of space and serious consequences if your OS partition fills up.
2. Disk encryption is very straightforward if you use separate OS and data partitions. You literally just tick a box during the install and enter an extra password. It won't upset Windows any more than a normal install does (i.e. Windows might think it's corrupted, but won't do anything without your input). With one partition for everything, it's still possible, but the encryption will be much weaker and handled by the bootloader in a somewhat clunkier way, and I'm not sure if Mint even supports that setup.
3. I don't have much experience with this myself, and certainly not on Linux Mint, so I'll leave this one to other commenters.
4. Synaptic is just a fancy frontend to APT, and I think Mint also has something called mintInstall, which was just an apt frontend back when I used it, but I think it also supports Flatpak now. It's entirely up to personal preference as to which UI you prefer. I do recommend you set up Flathub if it's not there by default, as it gives you access to a ton of useful apps that can't be packaged by Debian, Ubuntu, and Mint for various reasons.
5. Don't download software from random websites unless it's absolutely necessary. Chances are, their version either won't work well, if at all, or will break your system. Try APT first, Flatpak second, everything else is a last resort option. If a program you used on Windows doesn't have a (working, native) Linux version, try finding and learning to use an alternative that is in the APT repositories before downloading the Windows version and using it on Wine. Back up your most important files from Windows before installing Linux in dual boot, just in case you make a mistake somewhere. To answer the last question, stick to the default terminal emulator and Firefox installation unless there's a feature you really want in another one; the distro's developers picked them for a reason, after all.

This is an interesting comment, actually, because instead of hating on the new shows and comparing them to the old ones, Matt's hating on the old shows for being politically correct and saying DS9 and Voyager, the shows that were currently airing as of 1999, are the good ones. Even though DS9 was more diverse and less subtle about its themes, compared to TNG.

Imagine if Dave Cullen, Doomcock, Midnight's Edge, Nerdrotic, etc. dedicated their careers to saying that the new Star Trek shows were AWESOME because they were less woke than TNG and DS9. That's what this is.

VLC's file format support is amazing for a project that rolls its own codecs, etc, but it's missing some important features for me on the music front, primarily gapless playback and library management. I generally prefer to use software tailored to my DE. I've yet to find a better video player anywhere though; GNOME Videos and Kaffeine come closest and are a little easier to use, but are still far away from VLC's capabilities.

Isn't Proxmox intended for servers whose only use is to run VMs? Why not go for a traditional desktop distro like Mint and run KVM, QEMU, or VirtualBox on it?

Anyway, I have heard something like this, but it probably depends on the anti-cheat. Some might run in kernel mode to deliberately detect VMs. Others won't care if you use a VM.

Depends on a few factors, AFAIK as a non-lawyer. If the license allows closed-source derivatives (i.e. is permissive rather than copyleft), then anyone can create a closed-source version with all of the contributors' changes, including the original maintainer. And anyone can choose to keep it open-source. The community contributions still to some extent belong to the contributors, though the license waives most of their rights.

Some projects are copyleft, but contributors are required to sign a license agreement (a CLA) which allows a single entity to change the license as they desire, including to closed-source - this is a good reason to avoid such projects. The contributors don't own their work in such a case, but they can still fork the old project as it was before being taken closed source.

In a copyleft (e.g. GPL) project with no CLA, it's illegal for anyone to make a closed-source version, and a major contributor could sue even the maintainer for doing so.

In all such cases, the change to a closed-source model does not erase the existence of the open-source code with community contributions. A fork is always possible.

To be honest, I've never used or heard of a keyboard or mouse that doesn't work with Linux. The space is pretty well standardized so generic drivers work for everything. I don't have experience with keyboard layouts that aren't English QWERTY, though. The safest option would be something basic from a major brand, extra stuff like RGB is not 100% guaranteed to work.