Christian Nennemann
84ec822823
Technical comparison showing QuicProChat's differentiation: - Only mesh protocol with MLS group encryption + PQ-KEM - Multi-hop routing + LoRa support (like Reticulum) - End-to-end crypto (relays see opaque ciphertext) Honest about tradeoffs vs mature alternatives.
4.5 KiB
4.5 KiB
Summary
Why quicprochat?
- How quicprochat Compares to WhatsApp, Telegram, and Signal
- Comparison with Classical Chat Protocols
- Why This Design, Not Signal/Matrix/...
- Mesh Protocol Comparison: Reticulum, Meshtastic, Briar, Berty
Getting Started
- Prerequisites
- Building from Source
- Running the Server
- Running the Client
- REPL Command Reference
- Rich Messaging
- File Transfer
- TLS in quicprochat
- Certificate Lifecycle and CA-Signed TLS
- Docker Deployment
- Mesh Networking
- Demo Walkthrough: Alice and Bob
Architecture
- Architecture Overview
- Protocol Stack
- Crate Responsibilities
- Service Architecture
- End-to-End Data Flow
Protocol Deep Dives
- Protocol Layers Overview
- QUIC + TLS 1.3
- Protobuf Framing
- MLS (RFC 9420)
- Hybrid KEM: X25519 + ML-KEM-768
Client SDKs
- SDK Overview
- Wire Format Reference
- Rust SDK
- Go SDK
- TypeScript SDK and Browser Demo
- C FFI Bindings
- WASM Integration
Cryptographic Properties
- Cryptography Overview
- Ed25519 Identity Keys
- Key Lifecycle and Zeroization
- Forward Secrecy
- Post-Compromise Security
- Post-Quantum Readiness
- Threat Model
Wire Format Reference
Design Rationale
- Design Decisions Overview
- ADR-002: Cap'n Proto over MessagePack
- ADR-004: MLS-Unaware Delivery Service
- ADR-005: Single-Use KeyPackages
- ADR-006: SDK-First Adoption (No REST Gateway)
Implementation Internals
- GroupMember Lifecycle
- KeyPackage Exchange Flow
- Delivery Service Internals
- Authentication Service Internals
- Storage Backend
- Server Hooks (Plugin System)
Roadmap
- Milestone Tracker
- Phase 2 + M4-M6 Roadmap
- Production Readiness WBS
- Auth, Devices, and Tokens
- 1:1 Channel Design
- Future Research Directions
- Full Roadmap (Phases 1-8)