I use watchtower to auto update everything.
Anything that needs a specific version for compatibility (Postgres mostly) is pinned to the major release.
Stuff occasionally breaks, but I have backups for that reason (if you don't, set that up now before anything else, they should be running daily at least and you should have 2 types of backup minimum).
If you want that style of UI use Zen browser, it's based on Firefox and doesn't require an account to use it.
Arc is just another crappy browser based on Chrome. The account requirement was and is a huge red flag.
The healthiest is to enable the option to only charge to 80% (or near there, depending on the phone you have).
Otherwise slower charging is better, if the wireless charging doesn't make the phone hotter than say 30C or so I wouldn't worry about using it. 45C is the limit for charging Li-ion safely, but it's better to be cooler.
FolderSync is a good alternative, more battery friendly too!
Yes there's always a chance corruption can happen from a hard power off, always keep reliable backups.
Current 18650/21700 Li-ion cells are a lot safer than they were 10+ years ago, less chance of thermal runaway and fires now.
Cell quality is important. You want to be using known good quality cells like those from Panasonic, Samsung, LG, etc..
How you manage temperature, charge and discharge is also really important, dendrite growth can cause cell failure in time. Charge temperature is extremely important. So you want to make sure you're using a smart programmable BMS where you can set up all the protections properly. Ideally one with as many temperature probes as you can find, 4 is good, 8 is better and some will have that many.
Otherwise making sure nothing can short out internally is important too, but it sounds like you're putting some thought into that. Most critical IMO from what I've seen on pre-made battery packs is making sure your series banks are well insulated from each other and have no chance of vibration causing the cells to wear through their heatshrink and touch each other.
They could be away and not checking on things until they get back.
Or potentially their github account was taken over somehow.
It has always been OK for me.
What do you mean by 'never loads'? Are you getting a DNS failure, is it failing to load certain resources, or is it just timing out on the initial connection?
Gotcha, that makes more sense when explained that way!
I'm excited to see where it is in another year or so, the idea of using public/private keys for logins is neat for sure.
Sure:
Proxmox backs up all my VMs/CTs nightly to the proxmox backup server I run as a VM with an external HDD attached to it. This keeps around 30 versions with a retention policy so I can go back pretty far if needed. These are full bootable images and include everything.
Restic (using Backrest to manage it), runs on any VMs/CTs with critical data, and backs up to Backblaze B2 every night as well, this is a more limited choice of the critical files that I'd need. Similar retention policy as the proxmox backup.
With both I try and do some full restores every month or two and test things out.