I resisted WhatsApp until we started cruising with our sailboat. So many processes require WhatsApp. In many places you can't do customs and immigration without it.
Well, maybe not 100% true. There might still be the remnant of an old paper-based process around, but since nobody uses it, it would be a recipe for spending days queuing in random offices.
Once we're back in Europe, it will be a happy moment when I can finally uninstall the app.
I will be trying git over Reticulum for my next project. Fully peer-to-peer including issue tracking and releases. Reticulum itself already moved over, maintaining GitHub just as a mirror
I think the reasonable way to look at LLMs is similar to how you'd work with junior developers. They can churn out code, but do need constant guidance. Of course, (some of the) real juniors will eventually become seniors. It remains to be seen if LLMs will.
The traditional longer-range P2P is HF radio and maybe Winlink email on that. APRS over HF is also possible, and Reticulum would be too if hams were allowed to use encryption.
On the passage from Panama to Polynesia we had daily HF radio contact with Hawaii and California. Sometimes radio weather was pretty bad, but generally it worked out.
In practice nowadays passage communications for 99% of boats is WhatsApp over Starlink, with maybe Garmin InReach as backup.
I think there are people playing with Halow with Reticulum. That's one advantage of having a multi-transport system. There is also a Bluetooth transport now:
https://salemdata.net/johnpress/?p=720
I'm looking at setting up rngit mirrors of all my repos on our boat NAS. Conceivably it also allows issue tracking and collaboration without centralized infra
More on http://bergie.iki.fi and https://lille-oe.de/
[ my public key: https://keybase.io/bergie; my proof: https://keybase.io/bergie/sigs/94Ea8rkF51hWAkqI5uBmafa01SABlUwEamPyaPswvoM ]