Same principle.
avidamoeba
Oh yes, this is useful!
VMs with external IPs would be enough, so your typical VPS. Updated the title.
Bonus:
This is how you fix intermittent disconnects under heavy load.
I gotta try. I'm planning to switch to it anyways. The Android client is open source so if something has to be changed it can be contributed or forked if the contribution isn't accepted.
Gotta treat for ya:
The three gnomes in a trench coat are the three from the left.
It looks like interest rates aren't high enough.
I recently tested the most recommended wiki software and I settled on Wiki.js. Trivial to setup with docker-compose. It stores everything in its database but can continually dump it in various formats and places. I have it dump to the local filesystem. It spits out Markdown files. It can run on SQLite but it defaults to Postgres which provides better search. It's got simple RBAC too.
And there's an OSS control plane replacement called Headscale although I don't know what's involved in using it. Researching and implementing it is my backup plan for when Tailscale turns to shit.
E: Just briefly parsed their docs, deployment and usage seem pretty trivial. There's no need to use forks of the clients either. You can give your Headscale url to the Tailscale clients on login and you're good to go.
So you're saying I should be running RAIDz2 instead of RAIDz1? You're probably right. ๐
So you're saying I should be running JBOD with backups instead of RAIDz1? You're probably right. ๐คญ