If you have any thoughts of making any money of the code that may be a reason to give the license some thought. Anything else, these days, is just a LLM away from getting re-written regardless of whatever license you use. For example there is a service that takes any code, uses one agent to create requirements and another to use those requirements to create a comparable program; the claim is that the second agent did not “steal” your code since it purely worked off requirements. Sure, it likely won’t be as good, but it allows someone to take a significant part of your code for themselves. That was, more or less, always there in the past is just that now is near trivial to do.

Also, there are projects that are just fake open source. Like a project I saw yesterday with a restrictive license, but then has a CLA.

• AGPL restrictive copyleft license – good
• CLA (Contributor License Agreement) — a legal agreement where you grant the project maintainers additional rights over your contribution, often including the right to relicense it under different terms – not good

So, that project at first sight appears like it is open, but because of the CLA the authors may just take whatever contributions you do to the project and then change it’s license.

https://www.lunanode.com/ Only one data center in Canada, but affordable and have used them for years without issues. VMs starting at $3.5/month

You still need some means of outside backup. Figure what you have covers majority of scenarios, so now we are getting into the highly unlikely, but highly impact full like “my house burned down and now I have no data”. Something like B2 (or some other block storage with comparable pricing) is worth exploring.

You also need to consider your usage pattern like whether you may need to retrieve data (some providers charge for bandwith in / out). I would suspect most of the time between your ZFS snapshots and your disk you are covered.

Also, recommend to not leave the disk plugged in at all times for the scenario I mentioned: Your machine is compromised and the attacker encrypts data to ask for ransom; very low probability (I suspect those are mostly against companies), but really doesn’t hurt to prevent against it.

Suggest:

• Frequent ZFS snashots. There are scripts to make this easier like zfsSnap
• Two external backups which you rotate weekly [1]
• Instead of borg backup of ZFS pools if you have another machine you could sync the volumes to another machine or even use rsync to another machine of the data [2]

You did not mention where the target of the borg backup is, but you want an external service. I believe there is a service that works wells with borg backup, but have not used it.

Notes [1] Spinning disks are affordable. I suggest at least 2 because if you only have one and your machine was compromised, think disk encrypting malware, you disk may be encrypted too. Also, if the disk dies there goes your external drive backup

[2] If you have another machine with enough space to host a copy that is a good option. Also, there are services that offer backup/disk VMs. They have very slow CPUs and affordable disk. Those may be work checking

1 of which is off-site (in a safety deposit box, for example)

A potential compromise these days may be a block storage service. Safety deposit box is good, but because of it’s inconvenience people are very likely to do it seldom, which defeats the purpose.

I think this article Agentic coding impact on oss is related. In this case the author is outright saying “don’t submit PRs”, but in many other cases authors are not catching up with PRs so people just fork.

All in all, I think the impact of LLMs in open source will likely be significant over time.