alt Hacker NewsMesh networks are the foundation - they are essential to disaster resilience. Then what services to run over them ?
Real time chat: wild unsecure simplicity proven to run anywhere (IRC), bells & whistles with contemporary security (Matrix), some mesh native that almost no one knows ? What about post-disaster onboarding of actual users ?
Store & forward messaging: SMTP & friends may work nicely, but with actually distributed servers - in each local disaster POP. Also needs timeout and retry parameters to keeping stuff in queues practically forever.
Forums: anything better than ol' NNTP ? Other protocols merely adopted intermittent indirect connectivity - NNTP was born in it !
Is anything more sophisticated or more interactive realistic for actual disaster ?
An onboarding kit with clients for each major OS (à la AOL CDROM !) might be handy too, for snearkernet distribution over USB dongles.
Replies
I think the point of the article is not to use that mesh network as a replacement for internet. I think the author's idea is that the mesh network would provide the "resilience club" a communication channel while they work on recovering the regular internet.
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.