Personally, I would put one of the 990 in the server, use it as system drive + storage for databases and such. Then, the EVO in NAS to store backups, as it’s not very bandwidth sensitive and saves a little bit of lifespan out of the main SSD. And probably an extra copy of your restic repository onto the external 2TB SSD (though I would store that extra backup offsite on Backblaze B2)

Oh, and you should probably set up restic’s rest-server, it makes backuping from other computers really easy (easier than SFTP, which I had issues with)

For me the most interesting piece from the Mastodon thread is the fact that the Motorola partnership was born out of Google making it more difficult for non-OEMs to get access to AOSP source code (emphasis mine):

Google replaced pushing Git tags for certain source code with obtaining source code via Google Drive after making a request through Google Forms. It’s completely ridiculous and they’ve gradually become very slow at handling requests. They’re in clear violation of the GPLv2 now.

[…]

These changes won’t negatively impact GrapheneOS on upcoming Motorola Mobility devices. In fact, it’s a major part of why our partnership exists. It only negatively impacts Pixels and hurts Google more than anyone else. Google wants to make Pixels worse for no apparent reason.

This also means that in the future Motorola devices will get faster security updates on GrapheneOS than Pixels.

It’s frightening how the OSS ecosystem mostly centralized around GitHub. I’ve been trying all afternoon to debug issues with some libraries and most search results linked to GitHub… which spat out errors every single time.

You should take a look at Just The Browser, though you have to run it regularly to keep up with new Firefox releases.

Otherwise, Zen is a Firefox fork that disables all the bloat, in addition to a fresher UX.

I just set it up following your comment but I cannot figure out how to set it up in order to type in different languages without changing keyboards.