If you have legs harpooned to the deck on touchdown, presumably you can use much shorter legs (and therefore lower mass), as you're no longer depending on their length to prevent toppling?
Whenever I've tried to use Time Machine over the network, to a NAS or even to another Mac, it craps out after a few months and says the backups are invalid and asks to start again from scratch.
Advice seems to be 'only use it with external drives' and then every time you plug the drive in it wants the password.
For the last several years I've very happily used it over SMB to ZFS (with autosnaps) for this very reason, and wrote an AppleScript to automatically "verify" it every week or so.
Once or twice a year it gives a verify error (i imagine this is because a plug gets pulled halfway through a backup on one side or the other), and I just have to go find the last verified date, zfs rollback, and then re-verify. Afterwards it picks up where I left off, and the historical backups are preserved.
Wish it didn't require this extra effort in the first place, but much better than having to nuke and pave every time.
Even better, it's working great over Tailscale so I can even use it remotely. Only big hiccup I ran into was figuring out some ZFS setting about quota vs refquota (something like that) to have the Time Machine's (artificial) space limit match the ZFS quota so that Time Machine would prune the oldest backups appropriately (otherwise the ZFS snapshots took up an unpredictable amount of space and Time Machine would unexpectedly get out of space errors before hitting its space limit).
I used to get that constantly when I was backing up to a Synology NAS. I switched to an ASUSTOR AsusFlash NAS connecting over SMB and haven't had a single problem since. New NAS is M.2 based and can easily saturate its 10gbe link.
Side note, Synology is dead to me. Synology became consumer hostile with trying to force you to use their drives, they don't have good small scale M.2 options(at least as of last year when I upgraded), and their stuff doesn't even work for me reliably.
- change the temporary directory names we've been using - bin sounds like its for unwanted files, dev sounds like its for development, etc needs a better name. Its silly
I've personally seen someone ask a question, "My cat keeps jumping on my keyboard. Is there anything I can do to make sure she doesn't accidentally type a valid Unix command while I'm AFK?" And the answer was, "When you leave the keyboard, type "cat" and press Enter. That will put Unix in cat mode, where it will be protected from cats typing random characters." :-) (That's not verbatim, it's from vague memory of something I saw a couple years ago).
But then you need someone to maintain/look after that automation, and they'll be more expensive than two Brendas
And now if one of the Brendas wants to change their process slightly, add some more info, they can't just do it anymore. They have to have a three way discussion with the other Brenda, the automation guy and maybe a few managers. It will take months. So then its likely better for Brenda to just go back to using her spreadsheet again, and then you've got an automated process that no longer meets peoples needs and will be a faff to update.
For the record, I wouldn't usually use Brendas as a collective noun like this, it feels a bit wrong, but my aim was to make sense in context of the above comment.
The best way to think about LLMs is to think of them as a Model of Language, but very Large
reply