Summary:
As the world becomes increasingly dependent on Internet connectivity, the likelihood of significant disruption increases. In times of natural of manmade disaster, alternative, secure means of communication will be needed. This project aims to satisfy that need. Security and distributed architecture will be prioritized.
Architecture:
Security of the network will rely on public/private keypairs. This allows encryption to intended recipients and digital signature for message integrity. The distributed message database will be maintained by numerous peer-to-peer 'core' nodes. Backup sync mechanisms between core nodes, such as HF radio, will be explored. Messages will be retained by core nodes for a minimum of 180 days, allowing on-demand pickup for off-grid users and reception by multiple client applications. End user connections will be made to 'endpoints', which will usually be colocated with core nodes. Endpoints allow a broad range of interfaces to the messaging network, including web API, satellite, radio, even paper. Endpoints may require an optional network key for private access through high-cost media (satellite, etc.) and may blacklist or rate limit senders to prevent abuse.
What It's Not:
The Resilient Messaging Network is not intended as a replacement for instant messaging apps like Signal and SimpleX. There will be no app with Apple/Google push notifications, and a maximum message size may be enforced to limit database replication. Connections are intended to be made on a 'pull' basis.