Btrfs doesn't have encryption, so you need to do it with luks to an mdadm raid, and build btrfs on top of that. Luks on mdadm raid is known to be slow, and in general not a great idea.
Why involve mdadm? You can use one btrfs filesystem on a pair of luks volumes with btrfs's "raid1" (or dup) profile. Both volumes can decrypt with the same key.
The baby god event was never officially released, so this actually didn't canonically happen.
It was released. The Azure Flute and the event where you meet and battle Arceus in the Hall of Origin in DPPt was indeed never released, but this is different.
Arceus had various distributions in 2009-2010; the US one was at Toys R Us for example. Trading that legit Arceus to HGSS and then bringing it to the Ruins of Alph triggers this event which takes you to a special location where you can choose one egg of either Dialga, Palkia, or Giratina.
It is open source, but had some controversy. Most prominently the addition of telemetry a few years ago, which was never included in the builds managed by Debian or most other distro maintainers. They also added a Contributor License Agreement which lets the Audacity project change its own license (even to a non-foss one, though they promise they won't) without needing to have the change approved by any individual developers.
Even their earliest "uncarrier" features weren't without issue. Making certain services (spotify, apple music, youtube, netflix, etc.) not count against subscribers' data caps, while continuing to enforce data caps for other uses, goes against the spirit of net neutrality. This also includes throttling video streams by default to force lower quality (with opt-out on their site).
Promos like a free pizza on Tuesdays seems like a neat optional perk on the surface but their existence fundamentally mean subscription expenses on cellular network service are partially going towards things that have not even the slightest tangential connection to the service.
To the contrary, I would expect the sample to skew more towards people who have a heavily customized X session and strong opinions about window managers while drastically underrepresenting average GNOME users who stick with the default Wayland session. Someone who likes their custom setup can still be waiting for a Wayland equivalent while casual Ubuntu users have been defaulted to Wayland on new non-nvidia installs since early 2021.
I have configured custom Android kernel builds to enable more USB drivers, enable module support, and tweak various other things. For one tangible example of the result: I could plug in a USB Wi-Fi adapter and use it to simultaneously connect to another Wi-Fi network with the internal NIC while also sharing my own AP over USB. On an Android device of all things. I have also adjusted kernel builds for SBCs (like Pi clones) to get things working at all.
I have never seen any reason to configure a custom kernel for my own desktop/laptop systems. Default builds for the distros I've used have been fine for me; if I'm ever dissatisfied with anything it's the version number rather than the defconfig. The RHEL/Rocky kernel omits a few features I want (like btrfs) but I'd rather stick to other distros on personal systems than tweak a distro that isn't even meant for tweaking.
You joke, but it really exists: the company that acquired uTorrent 17 years ago now sells an ad-free version of their current torrent client as "BitTorrent Pro" for USD$20/year, or alternatively as part of a VPN service bundle for $70/year.
Needless to say, stick with FOSS clients like qBittorrent/Deluge/etc instead.
Nonfree media codecs like HEVC/h265 are affected by US software patents. Distributing them from US servers without paying license fees to MPEG LA can put the host at risk of lawsuit. VLC, deb-multimedia (Debian), and RPM Fusion (Fedora) all avoid that by hosting in France, but even with those sources enabled patent issues can break things like hardware acceleration. Free codecs like AV1/VP9/Opus avoid all these problems.
Microsoft is US-based and can't avoid those per-install fees. They could cut the profit from every single Windows license but apparently chose not to.
I just uploaded a mirror of the wiki to https://codeberg.org/zarenki/yuzu-wiki/src/branch/master/Building-for-Linux.md
Downloaded it a week ago, so might not be the most recent change.
The passive adapters that connect to DP++ ports probably still rely on this HDMI specific driver/firmware support for these features.
I would not count on all major distros maintaining support for processors as old as Core 2 forever.
RHEL 9 in particular (and by extension CentOS Steam, Alma, Rocky) already dropped support for all of the processors affected by this breakage since 2022.
Linux systems often group these CPU feature set generations into levels, where "x86-64-v2" requires SSE4 and POPCNT (Nehalem/2008 and newer) and "x86-64-v3" requires AVX2 (Haswell/2013 and newer).
Ubuntu and Fedora are already evaluating optimized package builds for both v2 and v3 but haven't announced any plans to drop baseline x86-64 yet; I wouldn't be surprised to see it happen within the next two years. Debian is a relatively safer bet for old hardware.
I feel like that purpose has already been undermined by various changes to copyright law since its inception, such as DMCA and lengthening copyright term from 14 years to 95. Freedom to remix existing works is an important part of creative expression which current law stifles for any original work that releases in one person's lifespan. (Even Disney knew this: the animated Pinocchio movie wouldn't exist if copyright could last more than 56 years then)
Either way, giving bots the 'right' to remix things that were just made less than a year ago while depriving humans the right to release anything too similar to a 94 year old work seems ridiculous on both ends.