RECLAIM

🔧 How Reclaim Uses P2P Technology

1. IPFS Integration (InterPlanetary File System)
   Content is addressed by its cryptographic hash, not its location. When you request a file, you receive it from the nearest peer who has it, not from a central server. This means:
   • Content cannot be deleted by taking down a single server
   • Files load faster as they can come from multiple sources
   • Duplicate content is automatically deduplicated
2. Device Synchronization
   Your bookmarks, settings, and browsing data sync directly between your devices using encrypted P2P connections. No cloud server ever sees your data. Run earthreclaim --sync-init to generate your sync keys.
3. Distributed Hash Tables (DHT)
   Peer discovery happens through DHT, allowing your device to find other nodes without relying on central directories. The network is self-organizing and self-healing.
4. End-to-End Encryption
   All P2P communications use modern cryptography. Your encryption keys never leave your device. Even if network traffic is intercepted, it remains unreadable.

🔧 The Hybrid Resolution Stack

Reclaim checks these sources in order, falling through until it finds an answer:

1. Local Cache (fastest)
   Domains you've visited recently are cached locally. Instant resolution, zero network traffic, complete privacy. Configure cache duration in Settings → DNS → Cache TTL.
2. P2P via Company (friends' domains)
   Query your trusted contacts on Company for domain resolution. If a friend hosts coolproject.earth, their node tells yours how to reach it. No central registry needed.
3. Federated Registries (community servers)
   Subscribe to community-run DNS registries. Academic institutions, activist networks, and regional communities can run their own registries. You choose which to trust.
4. Blockchain Registry (official .earth domains)
   For "official" .earth domains, resolution happens via blockchain lookup. Domain ownership is cryptographically proven—no authority can seize it without your private key.
5. ICANN DNS Fallback (legacy sites)
   For traditional .com, .org, etc., fall back to standard DNS. The old internet still works—we're extending it, not replacing it.

⌨️ CLI Commands

1. Register a .earth domain:
   earthreclaim dns register mysite.earth
   Generates a keypair and broadcasts your domain to the network.
2. Update your domain's IP:
   earthreclaim dns update mysite.earth --ip 192.168.1.100
   Signs the update with your private key and propagates via Company.
3. Add a federated registry:
   earthreclaim dns add-registry https://dns.academic-network.org
   Subscribe to a community registry for additional domain resolution.
4. Check resolution path:
   earthreclaim dns trace example.earth
   Shows exactly how a domain was resolved (cache, P2P, registry, or fallback).
5. Export your domains:
   earthreclaim dns export --format json > my-domains.json
   Backup your domain ownership keys and records.

🎛️ How EarthSearch Works

1. Personal Index Curation
   Add trusted sources to your index: earthsearch add-source https://example.org
   Remove sources you distrust: earthsearch remove-source example.com
   Your index is yours—export it, share it, or keep it private.
2. Community Index Sharing
   Subscribe to curated indexes from communities you trust. A medical professional might share their vetted health sources. A historian might share primary source archives. Indexes are cryptographically signed so you know they're authentic.
3. Local AI Ranking
   The AI runs entirely on your device. It learns your preferences from your interactions but never sends data anywhere. Train it by marking results as helpful or unhelpful. Over time, it surfaces what you actually need.
4. Transparency Mode
   Toggle earthsearch --explain to see exactly why each result appears. No black boxes. No hidden manipulation. Every ranking decision is auditable.
5. Federated Crawling
   Contribute to the network by allowing your device to crawl sites (opt-in). The collective index grows through distributed effort, not corporate data centers.

📋 How to Continue the Project

1. Repository Access
   The complete source code is hosted at: https://github.com/earthiverse42/earthservers-reclaim
   Fork the repository immediately if you intend to continue development. The code is licensed under open-source terms allowing continuation by anyone.
2. Build Instructions
   git clone https://github.com/earthiverse42/earthservers-reclaim.git
cd earthservers-reclaim
cargo build --release
   Requires Rust toolchain, Servo dependencies, and GStreamer libraries. Full build documentation is in BUILDING.md.
3. Key Dependencies
   
   • Servo browser engine: https://servo.org
   • GStreamer: https://gstreamer.freedesktop.org
   • Rust: https://rustup.rs
   • IPFS (for P2P features): https://ipfs.tech
4. Architecture Overview
   The codebase is organized into modules:
   /src/browser — Servo integration and tab management
   /src/media — GStreamer player and media handling
   /src/p2p — IPFS and DHT networking
   /src/dns — Hybrid DNS resolver and .earth domain management
   /src/search — EarthSearch AI and indexing
   /src/ui — User interface components
   Start with main.rs to understand the application flow.
5. Community Resources
   
   • Discord: discord.gg/earthservers
   • Website: earthservers.net
   • Issue tracker: GitHub Issues on the repository
6. Design Philosophy
   Always remember the core principles:
   • Privacy first — no telemetry, no data collection, local-first
   • Open source — transparency in all things
   • Community owned — no single point of control
   • Earth conscious — efficient, sustainable technology
   • User sovereignty — the user controls their data and experience
7. Financial Sustainability
   The project is designed to be sustainable through:
   
   • Optional donations and sponsorships
   • Earth Store revenue sharing with developers (planned)
   • Enterprise support contracts (future)
   Never compromise privacy for profit. Never sell user data.