Ensuring Reliability and Trust
Consistent Reliability: Adhere to schedules. If a radio check-in is at dawn daily, never skip without reason. Predictability builds trust in the network.
Honest Reporting: Avoid spreading false info. Misleading allies or lying can break the network’s value. Accuracy is currency in a trust-based system.
Anonymous Drop Points: If trust is low, messages can be left in sealed caches. Others retrieve them later. This reduces confrontation or suspicion. Witness Protocol: Sometimes send two couriers to confirm the authenticity of a message—if both recount the same message, trust grows.
Conflict Resolution: If disputes arise (e.g., someone claims a message was never delivered), have agreed-upon methods (like checking logs or verifying at a secondary hub) to settle it fairly.
Core Elements of an Offline Network
Nodes and Hubs: Identify central points (your base, a neighbor’s settlement) as “hubs” where information concentrates. Surrounding smaller outposts act as “nodes” connected by various channels.
Communication Channels: Radio relays, courier routes, signal mirrors, and message drops. Each node might favor a different method, but all must integrate into a common system.
Protocols and Schedules: Set standardized times for radio check-ins or courier arrivals. Routine fosters predictability—everyone knows when to listen, look for signals, or expect a runner.
Shared Frequency Lists: If using radios, distribute a list of agreed frequencies and times to tune in, ensuring all nodes know where and when to connect.
Offline Communication Networks: Why Build Offline Networks?
Start Small: Link two communities first, then expand as trust and resources grow. A phased approach builds confidence and experience.
Dry Runs: Send a test message and see how long it takes to reach another community and for a response to return. Evaluate delays and potential improvements.
Scenario Simulations: If a node fails (e.g., a relay station loses power), can the message reroute through another node or method?
Feedback from Participants: Are couriers overworked? Are radio operators confused by too many frequencies? Adjust accordingly.
Offline Data Exchange and Archives
Data Dumps via Couriers: Send USB drives or memory cards by courier to share large document collections or updated “encyclopedias” of local knowledge. Recipients then integrate that data into their own archives.
Security and OPSEC
Train everyone to suspect unusual messages—verify authenticity first.
If you suspect a recipient is compromised, send a test message with a known false detail —see if it spreads.
Communication Through Notes and Letters
Message Drops: Pre-arrange dead-letter boxes or hollow logs where notes can be left safely for allies.
Courier Systems: Send written letters via trusted runners. If lost, at least you haven’t revealed secrets vocally.
Physical Delivery: Runners and Couriers
Short, Secure Messages: Give couriers sealed envelopes or coded notes. Multiple Couriers: If message is vital, send two couriers by different routes.
Time-Based Exchange: If meeting someone daily at noon in a neutral spot to exchange messages, reliability improves trust and consistency.
Psychological Benefits
Building Trust: Consistent, honest communication fosters trust among survivors, essential for stable alliances. Without it, fear and suspicion dominate interactions.
Track a message through the whole relay
For a routine relay exercise, give a message an identifier, date, sender, intended recipient and requested reply. At each agreed handoff, record receipt and the next destination. Keep the wording intact rather than asking each person to paraphrase from memory. The final recipient should acknowledge the identifier so the originator can distinguish delivery from an assumption. Test what happens when one relay point is unavailable and when an old message arrives late. A dependable offline network needs a way to detect missing, duplicated and outdated messages, as well as a path along which messages can travel.