I think I’ve tried nearly every monospace typeface over the years and I’ve finally settled on JetBrains Mono for more than 2 years now, though IBM Plex Mono is a close second.

Looks great! I’ll definitely give this a try!

You can go with something like this if you want a clean solution.

I use a drive dock station for my backup drives, and I have a few of these for one-offs too.

Crucial is fine. It’s commonly found in corporate and government workstations.

I don’t use RCS myself, but there are recent posts on the GOS forums and it appears to be working fine once all of the prerequisites are installed.

Sure, like I said above, GOS doesn’t at all prevent you from rooting the device. They only discourage it from a security point of view. Regarding MicroG, I’ve never had need for it myself but I’ve read many other posts over the years from users who have installed it on GOS in lieu of Graphene’s own implementation.

I would argue that overall GrapheneOS provides more control over the OS than some other Android-based operating systems.

They don’t.

You can root GOS like any other Android-based OS. It’s just highly discouraged, completely unsupported and, in the opinion of the GOS devs, you will no longer be considered to be running GOS since you are compromising the core OS by doing so.

You’ve clearly done your homework, and you’ve gotten a lot of good feedback already, so I’ll just add a few points…

• Storage options: Personally, I’d replace the existing drive with the highest capacity I could afford. In an ideal situation, I’d keep the host on another drive (NVMe or flash) and dedicate the large drive to a single partition of data storage.

  In my own mini-PC (8th gen NUC), I’ve got a smaller NVMe for Proxmox and a single 8TB internal SSD for data.

• Encryption: If you’re going to bother with encryption, I wouldn’t half-ass it. Why bother at all if you’re fine using auto-decryption or a weak password that will be guessed with any sizeable effort? Just lock it down with a strong password and decrypt/mount the data drive after any reboot; making a shell alias or script for this is trivial. You’re likely not rebooting the server more than once a week anyway.

• Budget/Specs: I get the sense you don’t have much budget right now, but knowing your hardware would help in suggesting solutions. Do you have an NVMe slot? What is the make/model of the motherboard and case?

• Filesystem: For simple storage, this really doesn’t matter and Ext4 will probably be fine. It’s a mature, robust, no-frills filesystem which is perfect for bulk file storage (docs, music, videos, etc.), but Btrfs would be fine too if you want more options.

• USB Docking Stations: I’ve had really good experiences with USB docking stations like this one, and I currently use it for attaching my backup HDDs each month. I wouldn’t want to rely on them for realtime data access, but they do work wonderfully for backups and one-off drive access.

Your options will depend on many things…

• How much storage is needed?
• Is RAID important to you?
• Is power usage a concern?
• Noise level?

I don’t know how demanding photoprism is, but you could probably do fine with a refurbished i5/i7 Dell Optiplex or similar, with one or more SSDs added to it. If money is really tight and storage needs are high, you could go with mechanical drives instead.

The problem with enterprise servers is that are generally very loud and use a lot of power…not unlike adding a second refrigerator to your environment. In my opinion, they’re not worth it unless you have a specific use case (training for a career, etc.).

The dropbear method is more secure overall, and I plan to incorporate it as well when I find the time to wipe/reinstall my server, but it’s arguably not as easy or simple, which is what OP requested.

As mentioned elsewhere, the easiest method is to encrypt only the data drives. This way you can secure shell into the server upon restart and decrypt the data. I’ve been using this method for years now without issue.

You’ll need to provide specifics if you want solutions to many of these issues.

• What exactly isn’t working with your Yubikey?
• Which bank apps? Did you check the compatibility list maintained by GOS?
• Which apps aren’t working without Google Play?

For the keyboard, there are several FOSS keyboards which support spacebar navigation, but you can also install Gboard and simply disallow any permissions, including network access.

Regarding Signal, this would be a reality for anyone with a non-Apple device. You may need to find a compromise and simply use SMS, RCS, or even just email when dealing with certain people.

There will always be one-off features available only on other devices or platforms. Only you can decide whether they are worth the cost of security and privacy.

I’ve been super happy with my 8th gen Intel NUC i5. I put it in an Akasa Turing fanless case, installed an NVMe for host OS, and an 8TB SSD for data. It’s low power and so quiet that I couldn’t imagine ever using fans again.
I also have a USB 3.2 drive dock for external backup HDDs, but I only turn it on when actively doing a monthly backup.

8TB holds more media than I’ll ever need, but I do trim movies and shows regularly. For some, 8TB won’t be anywhere near enough, and SSDs exceeding this are ridiculously expensive.

If ambient noise is a concern, I’d go with an SSD. If money is tight, an HDD will give you the best value.

My server is in an otherwise quiet home office/sitting room, so I went with an 8TB SSD (870 QVO). Spinning disks make a fair bit of noise just waking up, let alone the actual file operations.

Craigslist is still superior in the PNW, at least in my experience.

Completely anecdotal, but I generally find more success with servers outside of North America. Definitely helps with reddit and imgur.

See my follow-up post elsewhere here. Sounds like you might not have an always-online device to keep others always synced, and/or the devices you’re using to add entries aren’t online when you do. Might consider using a designated device for database modifications.

That used to happen to us before we started using SyncThing (and before we had data plans on our phones).

By the time we migrated to it, we had a home server running 24/7 and this ensured that at least one device in the chain was always online, had the latest version of the database, and pushed it to other devices as they came online. Our phones also have data plans now, so things generally sync in realtime which helps avoid issues.

If you don’t have at least one always-online device, I think the next easiest way to avoid sync conflicts is to modify the database from one designated device. That way even if a conflict does arise, you’ll know which device is always correct.

For resolving the conflicts, I would open both databases, sort by modified, and review the latest changes in each.

KeePass, and more specifically the KeePassXC (desktop) and KeePassDX (Android) ports.

My wife and I have shared a single KeePass database for about 15 years now and I couldn’t imagine switching to anything else.

My reasons have remained the same over the years:

• Free and open source
• Offline (but supports cloud sync)
• Lightweight
• Cross platform
• Supports autofill

I would never entrust the management of my credentials to a 3rd party online service. They’re an easy target (it’s only a matter of when, not if they are breached), and they could go out of business at any time.

We don’t use cloud storage for anything these days, but we keep the KP database (and many other things) synced across more than 7 devices using SyncThing, another amazing FOSS project.