This page describes strategies for coordinating viral campaign messaging in a decentralized system. The goal is to prevent people from being contacted multiple times by different campaigners while preserving privacy, local autonomy, and the relational magic of the approach.
# Problem As viral waves spread through different communities, it becomes increasingly likely that: - Someone already contacted may be contacted again by a different node - A person who already joined may be asked again - A friend receives the same message from two different people This duplication can erode trust, feel spammy, and reduce campaign magic.
# Layered Solutions To prevent this without centralized surveillance, we propose a layered strategy: ### 1. Consent Registry - A privacy-preserving database of **hashed identifiers** (e.g. salted phone/email hashes) - Each node checks the registry before contacting someone - Participants must **opt in** — it’s not a surveillance list ### 2. Invite Tracking - Each mobile app keeps a **local list** of who was invited (first name, nickname, or pseudonym) - Optional sync across nodes allows **friend-of-friend awareness** - Enables “I already invited her” coordination at human scale ### 3. Campaign Tokens - Each message includes a **campaign code** (e.g. `?wave=gen-z-hikers&node=skywalker`) - When a person responds or joins, the system logs their source - Future messages can check this to avoid recontact ### 4. Self-Marking Replies - Let people reply with: - ✅ “Already in” - 🚫 “No thanks” - ⏳ “Still deciding” - This response is stored in the app and optionally shared with their inviter or cluster ### 5. Do Not Contact Lists - Each node maintains a **local DNC list** - Shared with nearby chairs or trusted delegates - Prevents continued outreach to those who declined ### 6. Federated Bloom Filters - Use cryptographic **Bloom Filters** to share approximate, privacy-preserving info about who’s been contacted - These filters can merge across groups without exposing individual identities - Advanced but powerful for wide-area coordination
# Diagram
digraph OutreachCoordination { rankdir=LR; node [shape=box style=rounded fontsize=11]; Consent [label="Consent Registry"]; InviteTrack [label="Invite Tracking"]; Tokens [label="Campaign Tokens"]; SelfMark [label="Self-Marking Replies"]; DNC [label="Do Not Contact Lists"]; Bloom [label="Federated Bloom Filters"]; Consent -> InviteTrack; InviteTrack -> Tokens; Tokens -> SelfMark; SelfMark -> DNC; DNC -> Bloom; }
# Summary
This layered approach allows your viral campaign to:
- Respect the dignity and attention of every participant
- Prevent duplicate outreach
- Coordinate across federated groups
- Protect privacy
- Preserve the magic of human-to-human invitations
Each group can choose which coordination tools to use based on their needs and risk tolerance.
# See
- Layered Defence
- Viral Onboarding Waves
- wikipedia.org ![]()