My main reasons are sailing the high seas

If this is the goal, then you need to concern yourself with your network first and the computer/server second. You need as much operational control over your home network as you can manage, you need to put this traffic in a separate tunnel from all of your normal network traffic and have it pop up on the public network from a different location. You need to own the modem that links you to your provider’s network, and the router that is the entry/exit point for your network. You need to segregate the thing doing the sailing on its own network segment that doesn’t have direct access to any of your other devices. You can not use the combo modem/router gateway device provided by your ISP. You need to plan your internal network intentionally and understand how, when, and why each device transmits on the network. You should understand your firewall configuration (on your network boundary, not on your PC). You should also get PiHole up and running and start dropping unwanted inbound and outbound traffic.

OpSec first.

In comparison with other city-builders Wandering Village isn’t very deep. There isn’t much in the way of complex systems. The art is nice though and it’s fairly relaxing to play.

Timberborn is a lot more involved and there is a lot more depth to population management and economics, and it’s pretty fun when you get to the level of reshaping the ground to suit your purposes. My favorite challenge is to arrange to keep the whole map green through a drought.

Wandering Village is more like a story or adventure game with city-builder mechanics, so it kind of needs a proper narrative arc.

I played this through shortly after the release and it is really enjoyable, but once you’ve built and stabilized your town and used all the space there’s nothing else to do. You can keep walking through the world but it’s just an endless series of repeat biomes and there’s no more growth potential so none of the side quests are of any interest.

Adding some endgame content might really help this.

By the phone company.

Heh, that won’t stop a C-level from thinking that you just write code.

For individual projects the way this usually works is one of the larger companies that rely on the project hires the developer as an employee to maintain the codebase full-time and help integrate it with their internal processes.

Larger projects might form their own company and sell integration & support to other companies (e.g. Red Hat, Bitwarden).

Otherwise you’re basically dependent on donations or government grants.

There’s a Wikipedia article on this subject: Business models for open-source software

And there’s various industry opinions:

Demystifying the Open Source Business Model: A Comprehensive Explanation

How to build a successful business model around open source software

Open Source Business Models (UNICEF course)

I think monetization is easier for user-facing software though, which a lot of this material is written around, and harder for projects like libraries.

VPNs as a technology might not be illegal but circumventing the firewall certainly is.

Unless you are very vocal and high profile person no one will black bag you in a country of billion people, lol.

This is a bit of a misunderstanding about how things work in an authoritarian system. Sure, you might fly under the radar for awhile, but if you call attention to yourself (say, by getting caught trying to bypass the government firewall) and you are not high-profile, then it is very low-effort to make you disappear. Few will notice, and those that do will stay silent out of fear.

If you are more high-profile you still get black-bagged, you just get released after, with your behavior suitably modified.

Naomi Wu no longer uploads to YouTube.

Depends - how many family members do you have that the PRC might use against you? or who would miss you if the PRC black bagged you?

And there are hundreds if not thousands of them, plus a lot of automated tooling.

Beyond your eventual technical solution, keep this in mind: untested backups don’t exist.

I recommend reading some documentation about industry-leading solutions like Veeam… you won’t be able to reproduce all of the enterprise-level functionality, at least not without spending a lot of money, but you can try to reproduce the basic practices of good backup systems.

Whatever system you implement, draft a testing plan. A simpler backup solution that you can test and validate will be worth more than something complex and highly detailed.

I mean… exposed to each other, sure, but they’re all exposed to Syncthing and the public relays.

It is a fantastic idea to start your home server project on some e-waste hardware, and use it until you know specifically what features you’re lacking that you would need better hardware for.

Er, wait, are you using Syncthing for its intended purpose of syncing files across devices on your local network? And then exposing that infrastructure to the internet? Or are you isolating Syncthing instances?

The issue is more that trying to upgrade everything at the same time is a recipe for disaster and a troubleshooting nightmare. Once you have a few interdependent services/VMs/containers/environments/hosts running, what you want to do is upgrade them separately, one at a time, then restart that service and anything that connects to it and make sure everything still works, then move on to updating the next thing.

If you do this shotgun approach for the sake of expediency, what happens is something halfway through the stack of upgrades breaks connectivity with something else, and then you have to go digging through the logs trying to figure out which piece needs a rollback.

Even more fun if two things in the same environment have conflicting dependencies, and one of them upgrades and installs its new dependency version and breaks whatever manual fix you did to get them to play nice together before, and good luck remembering what you did to fix it in that one environment six months ago.

It’s not FUD, it’s experience.

This is also a great way to just break everything you’ve set up.

and you have to choose to boot into desktop mode to even mess with anything.

You say that like it’s a bad thing, but I think having the two separate modes is a fantastic setup. You get basically a console experience, smooth and straightforward and easy to use for just playing games, and you still have access to the underlying system anytime you want.

I recommend getting familiar with SMART and understanding what the various attributes mean and how they affect a drive’s performance and reliability. You may need to install smartmontools to interact with SMART, though some Linux distributions include this by default.

Some problems reported by SMART are not a big deal at low rates (like Soft Read Errors) but enterprise organizations will replace them anyway. Sometimes drives are simply replaced at a certain number of Power-On Hours, regardless of condition. Some problems are survivable if they’re static, like Uncorrectable Sector Count - every drive has some overhead of extra sectors for internal redundancy, so one bad sector isn’t a big deal , but if the number is increasing over time then you have a problem and should replace the drive immediately.

Also keep in mind, hard drives are consumables. Mirroring and failovers are a must if your data is important. New drives fail too. There’s nothing wrong with buying used if you’re comfortable with drive’s condition.

Until your WiFi driver stops getting updates.

“We do not break userspace.” ~ Linus Torvalds

I would always argue that any distribution which does not prioritize this principle is a hobby project, not a serious distribution for end users.

Which is fine, hobby projects are good, but they should be labeled accordingly to properly set user expectations.

GlaDOS