Post-disaster onboarding is complicated by app store lockdowns and the difficulty of sideloading. Heck, even establishing plain http or self-signed https connections is tricky on phones now.
I'm sure someone smarter than me has a toolkit for these things, I just don't know where to find it.
Store-and-forward-wise, NNCP is designed for this, but it's not widespread yet.
I was just thinking about this sort of thing the other day. Thinking if I need a techno 'bug out' bag, my Macs would be the most useless ones to waste the weight on because if anything happened I'd never be able to reinstall macOS without phoning home to Apple for an activation.
Trouble is a Linux-on-a-key that you've never used before, is still a long way from being productive without a network to install all the packages you actually want to use.
It takes me about a month after a reinstall or new machine, to feel like I've really spread my wings and have everything installed that I initially forgot about. So I guess the recommendation would be "daily-drive it for a month before refrigerating it". And at that point, you might as well just make it your everyday machine.
> Heck, even establishing plain http ... connections is tricky on phones now.
I had no idea. I guess this refers to app-store rules? Related to https://developer.android.com/guide/topics/manifest/applicat... and https://developer.apple.com/documentation/security/preventin... ?
Or is it even hard to browse to http webpages? (No problem on iOS that I see.)