As for timing, one could use the flock function to ensure only one process starts. Something like this (untested): flock -n ~/.htop.lock -c htop
RFC 3339! ISO 8601 has way too many weird formats that are allowed like today would be 2023-W41-2. See for example here.
At least always use git push —force-with-lease. It makes sure you are that the remote hasn’t changed since you lasted pulled. https://git-scm.com/docs/git-push#Documentation/git-push.txt---no-force-with-lease
When I researched what to use for my backup I found rsync.net. They have some nice features nobody else seems to support, like they support ZFS send/receive https://www.rsync.net/products/zfsintro.html
But in the end the price made me go with borgbase.com
I believe it just finds the user and not the post because the previous posts aren’t synced. So if you are the first user on your instance (eg lemmy.world) to look at that user, only the new posts that this user posts after you have subscribed are synced to the instance.