Offline Messaging Systems

Before networks fail, identify 3-5 neutral public meeting locations within your community (parks, landmarks, town halls, churches). Establish specific times using a 24-hour format UTC to avoid timezone confusion—use weekly intervals (Tuesdays at 14:00 UTC) or specific dates (15th and 30th of each month). Ensure all group members memorize these locations and schedules without written records. Create code names for each location so verbal communication doesn't identify actual places.

Never post meeting details online or in text messages before going offline. Choose locations with multiple entry/exit routes and natural gathering (crowds provide cover).

Select secure locations for leaving physical messages: behind loose bricks, inside hollowed books in libraries, waterproof containers buried 6-12 inches under mulch, or magnetic boxes under park benches. Use the "one drop, one pickup" rule—the sender leaves a signal (chalk mark, bent leaf, or small rock placement) in a publicly visible spot within 50 feet to indicate a drop is ready. The receiver checks the signal location first, retrieves the message, and immediately removes the signal marker. Rotate locations every 3-5 uses to prevent surveillance.

Avoid your own home or work as drop locations. Use gloves to avoid fingerprints and keep messages brief to reduce search time.

Use community bulletin boards, library notice sections, craigslist (if partially available), or create physical boards in shared spaces with group permission. Format messages as classified-style posts: "Lost golden retriever, answers to MAX, seen near Oak Park Tuesday." Code actual information into seemingly mundane posts about missing items or wanted items. Establish a key beforehand: the first letter of each line spells the message, or use the nth word method (every 5th word contains the real message). Check boards weekly at the same time, using different observers to avoid patterns.

Create plausible cover messages—they should look authentic to avoid drawing authority attention. Never reference the messaging system in other communications.

Identify 6-10 trusted individuals in different neighborhood zones who can safely carry written messages. Train runners on a standardized handoff routine: confirm identity using a prearranged phrase ("How's your garden growing?" → "Flourishing in spring"), exchange messages in sealed envelopes with no identifying marks, and take no longer than 5 minutes per contact. Establish a 24-hour relay schedule so no single runner carries critical messages. Runners should vary their routes and timing to avoid surveillance patterns. Create redundancy—each message goes to 2-3 different runners on different routes.

Runners can be detained or intimidated. Keep messages brief (under 200 words). Establish a protocol for runners to discard messages if stopped by authorities.

Use substitution ciphers (shift each letter by a fixed number: A→D, B→E, etc.), acrostic codes (first letters of sentences), or the "book cipher" method (letter positions in a predetermined reference text like a specific Bible chapter or dictionary page). Establish the cipher key and reference material beforehand. Example with shift cipher (shift of 3): "HELP" becomes "KHOI." For critical messages, use a double layer: first encode the message, then hide it in a seemingly innocent letter about everyday topics. Keep a written key in a secure location separate from coded messages.

Simple ciphers can be broken in minutes by trained analysis. Use only for low-security information or as obfuscation in dead drops. For sensitive intelligence, use this combined with other security measures like dead drops.

Create a handwritten one-page information summary (situation report, resource availability, hazard warnings) and distribute copies through the runner network every 3-7 days depending on circumstances. Design reports with headers: DATE, SENDER LOCATION, CRITICAL UPDATES (3-4 bullet points), RESOURCE STATUS (water/food/medical/fuel availability in your zone), NEXT COLLECTION POINT. Keep records in a simple log: date, message number, recipient confirmation. Establish a "dead drop library" where runners can leave copies of reports at designated dead drop locations for secondary distribution.

Physical records are discoverable. Destroy old reports after archiving critical information. Use water-resistant paper for outdoor drops.

Establish rules for all offline communicators: never mention the system by name in conversation, never combine knowledge of multiple message methods, vary your times to drops by ±15 minutes, watch for surveillance before approaching any location for 10 minutes minimum. Create a "compromise signal"—if any person is detained or threatened, they send a specific message to runners using a code word (like "seller is sick" in a classified post) alerting the network to pause activities. Rotate roles monthly—have runners become drop monitors, have drop monitors become message creators. Maintain absolute compartmentalization: participants should only know their immediate contacts, not the full network structure.

Surveillance can be visual, electronic, or informant-based. Security depends on discipline. One careless communicator exposes the entire network.

Require all critical messages to include a confirmation request: "Acknowledge receipt by leaving green chalk mark on southeast corner of park building." Set a 48-hour response window before resending via alternate method. For critical decisions, use the three-confirmation rule: send the same message by three different methods (dead drop, runner, bulletin board) within 24 hours and wait for majority confirmation before acting. Maintain a secondary communication method separate from primary systems—if dead drops fail, escalate to runners; if runners are compromised, activate message board system. Document contact attempts in a coded log with message IDs and confirmation status.

Lack of confirmation has led to missed warnings and failed coordination in emergencies. Assume at least 30% message loss in offline systems due to human error or compromise.