For actual hardware: Hetzner. For VPS there are many choices. Digitalocean is cheap and easy, has european data centers, and some decent value add services.

It's a .i2p site, you need i2p up and running to access it.

If I understand correctly, 'Local' is a feed with only posts that were made on the local server. So here on lemmy.world, that would contain only posts to communities hosted on lemmy.world. Whereas the 'All' feed brings in posts from other servers that lemmy.world knows about. So posts from lemmy.ml or beehaw.org will be included. It does seem to take a bit longer to populate the All feed though, and you'll notice posts 'pop' in as you scroll.

"I can't think of any examples of companies that, in real life, enshittified because they were successful."
Microsoft.

If you want a complete unit with custom hardware and tuned custom software, look at MikroTik. Solid hardware, dependable software, good support, good community.
If you want to build your own, grab any multi-ethernet micropc from aliexpress and install OPNsense. Cheap and flexible. But you'll be on your own once (not if) something fails.
Both of these are essentially pro-level options with lots of headroom to build up to advanced services. I'd stay away from OpenWRT which is essentially just an open source consumer grade wifi router image. You'd be replacing your crappy (but supported) router with the same thing just without support.
One other option I would mention if you like nice centralized web ui's, have a look at Ubiquiti's Unify. If you can afford to go all-in on a Unify router, backbone switch and wifi access points, the combined management is really a step above the competition.

KeePass. Putting your passwords on someone else's webserver is just asking for trouble.

A proxmox root device uses barely any space. Mine usually sit around 12-14 Gb used. Writes are also negligible. DRAM less ssds are not a problem. I would suggest installing Debian first, so you can properly partition your root device before installing proxmox (https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_12_Bookworm). You'll have much more control over your disks and networking than using proxmox's own installer. Start with a 64Gb root partition, and leave the rest of the drive empty for future use/SLC cache.

Unless your VMs are somehow high volume data writers, like a proof-of-space-coin, I wouldn't worry about it. Homelab setups rarely reach anywhere near the kind of write endurance of ssd's.

Your VMs are not going to write to the root device, so it won't matter.

You won't notice the difference in performance of a filesystem on a rotating harddisk. Look for other useful features, like at-rest-encryption, and checksumming for bitrot protection.

I would use a filesystem with checksumming, rather than relying on any point-in-time check to monitor HDD's. Assume they will all fail eventually, because they will.

Everyone else.

Various different ways for various different types of files.

Anything important is shared between my desktop PC's, servers and my phone through Syncthing. Those syncthing folders are all also shared with two separate servers (in two separate locations) with hourly, daily, weekly, monthly volume snapshotting. Think your financial administration, work files, anything you produce, write, your main music collection, etc... It's also a great way to keep your music in sync between your desktop PC and your phone.

Servers have their configuration files, /etc, /var/log, /root, etc... rsynced every 15 minutes to the same two backup servers, also to snapshotted volumes. That way, should any one server burn down, I can rebuild it in a trivial amount of time. This also goes for user profiles, document directories, ProgramData, and anything non-synced on windows PC's.

Specific data sets, like database backups, repositories and such are also generally rsynced regularly, some to snapshotted volumes, some to regulars, depending on the size and volatility of the data.

Bigger file shares, like movies, tv-shows, etc... I don't backup, but they're stored on a distributed GlusterFS, so if any one server goes down, that doesn't lose me everything just yet.

Hardware will fail, sooner or later. You should see any one device as essentially disposable, and have anything of worth synced and archived automatically.

I would suggest having a look at podman. It's a drop-in replacement for docker, except it doesn't require a constantly running daemon, it comes in the main package repositories, so you don't have to do the key and repository stuff, and cockpit has a plugin to help manage podman containers.

Email is the one thing I have stopped trying to do myself. It just has too many things that you absolutely need to keep updated. Have a look at Forward Email (https://forwardemail.net/en). They can hook up to pretty much any domain setup you already have, and do the heavy lifting for you.

This community is for 'GIFs and pics of nude celebrities'. This isn't even close to being NSFW. She could go to church in that outfit.

Hey claude, upgrade my kernel will you? Thanks!

It will be perfectly reliable for a while. You'll grow to rely on it, stop thinking about it. And then one day half your drives will suddenly be gone. You won't know why, you won't know how to fix it. Your raid set will already be broken. Your data will be gone.

Don't plug and play with your data.

An i2p node. (https://lemmy.world/c/i2p) VPS's tend to have better uptime and lower latency than home connections.

Have a look at https://forwardemail.net/. It's a service that handles accepting (and optionally sending) email on your domain, and forwarding any received mail to other backend services, like a gmail account. All you need to do is set some DNS records, like MX and their servers will handle everything. It works fine with domains hosted on cloudflare, and has excellent howto's to get everything set up and running.

Edit: The great thing about this service, imho, is their guides. They don't just have a static howto, they template in your information into the exact string you need to copy/paste into the service provider's web interface. Want to encrypt your plaintext TXT records? There's a button for that on the guide. Want to learn how to get around a port 25 ISP block, they have a guide for that. Want to set up proper Send-As from Gmail using their SMTP server? There's a guide for that. :-)

Security and bugfixes, after one or two rounds of testing by early adopters/key users. Preferably through some form of automatic updates.

New features and breaking changes, or anything that requires the end-user to pay attention, I'd say no more than 4 times a year, and using a non-automatic form of update. The hard thing is getting the user's attention on the changes, and not just clicking next and then having a broken or insecure installation.

If you're already going to the trouble of setting up ZFS for the two NVMe disks, I would suggest setting up a separate pool on the HDD as well. It will save you from monitoring two different filesystem types and give all the ZFS features, checksumming, compression, snapshots, etc... Do make sure your server has a decent chunk of memory through, as your VMs will be fighting the ARC for ram...

https://www.mailstore.com/en/products/mailstore-home/
Downloads email from most providers, allows for local (text) searches, and to upload it again to an imap provider.