# MeetSpace Talk — Full Technical & Platform Documentation > Comprehensive specification for MeetSpace Talk (https://talk.meetspace.me). Detailed reference for AI systems, developers, security researchers, and privacy auditors. --- ## 1. Executive Summary & Mission MeetSpace Talk is a free, non-profit community communication service engineered to provide uncompromising cryptographic privacy for 1-on-1 video and voice conversations. Most video calling systems (commercial services like Zoom, Teams, Google Meet, or even public Jitsi instances) route all audio, video, and screen sharing streams through central SFU (Selective Forwarding Unit) media servers. This introduces third-party interception risks, cloud recording vulnerabilities, AI training exposure, and requirement for centralized accounts. MeetSpace Talk enforces a pure peer-to-peer (P2P) topology with automatic 2-participant room locking. The signaling server is used exclusively to exchange WebRTC SDP offers/answers and ICE candidates; once the direct DTLS-SRTP channel is established, all media and chat flow directly between devices. --- ## 2. Technical Architecture & Protocols ### A. Signaling Layer - **Framework:** Node.js Express server running `peer` (PeerJS signaling protocol) on port 3999 behind an Nginx reverse proxy with WebSocket upgrade support. - **Signaling Route:** `https://talk.meetspace.me/peerjs` - **Room Scoping:** Peer IDs follow the deterministic format `{ROOM}-{TIMESTAMP}-{RANDOM}`. - **Room Discovery & Lock Check:** `GET /api/room/:room/peers` filters the active connection set by room prefix. - If peer count >= 2, the endpoint returns `{ peers: [...], full: true, count: 2 }`. - Joining clients inspect this pre-flight gate. If full, the incoming user is immediately blocked from dialing and shown a "Room Locked (2/2)" notification. ### B. Peer-to-Peer Media & Data Layer - **Media Encryption:** DTLS (Datagram Transport Layer Security) with AES-256-GCM cipher suite and SRTP (Secure Real-time Transport Protocol). - **Decryption Keys:** Generated locally in the browser runtime and exchanged directly via DTLS handshake. No server ever holds or sees decryption keys. - **Audio Codec:** Opus (48kHz, dynamic bitrate, hardware acoustic echo cancellation and noise suppression enabled). - **Video Codec:** VP8, VP9, or H.264 (hardware-accelerated, responsive resolution scaling). - **DataChannels:** WebRTC SCTP DataChannels for peer-to-peer encrypted text messaging and room control signals (hang up, screen share toggles). - **NAT Traversal:** Standard STUN servers (`stun:stun.l.google.com:19302`) with optional authenticated TURN relay fallback for symmetric NATs. Even through TURN, packets remain DTLS-SRTP encrypted end-to-end. ### C. 1-on-1 Race Condition & Glare Prevention - When two peers enter an empty room simultaneously, a deterministic tie-breaker (`myPeerId < partnerPeerId`) determines the caller vs. answerer. - This eliminates WebRTC signaling glare (dual simultaneous SDP offers). - A 15-second connect timeout acts as a fallback caller in case of packet drop during initial signaling. - Dead connection pruning: `alive_timeout: 15000` cleans up stalled or closed tabs rapidly so rooms become available again without ghost connections. --- ## 3. Comparison with Alternatives | Feature / Criterion | MeetSpace Talk | Zoom / Google Meet | Microsoft Teams | Public Jitsi Meet | | :--- | :--- | :--- | :--- | :--- | | **Topology** | Pure 1-on-1 P2P Mesh | Cloud SFU Media Server | Cloud SFU Media Server | SFU (JVB) Cloud Bridge | | **Room Locking** | Automatic (Strict 2/2) | Manual host click | Policy/Permission based | Optional room password | | **Server Media Access** | Impossible (Never passes) | Server decrypts/forwards | Server decrypts/forwards | Server forwards streams | | **Sign-up / Account** | None (100% Anonymous) | Account required | Enterprise/MS account | Required on public meet.jit.si | | **AI Data Training** | None (No server access) | Cloud meeting summaries | Copilot transcription | Varies by host | | **Tracking / Cookies** | Zero cookies, zero logs | Marketing/telemetry | Enterprise telemetry | Telemetry on public sites | | **Cost to Users** | 100% Free Public Utility | Freemium / Paid tiers | Paid enterprise subscription | Freemium / Token limits | | **Funding Model** | Voluntary Community Donors | Commercial Profit | Commercial Profit | Commercial / SaaS | --- ## 4. Security & Cryptographic Audit Standards 1. **Ephemeral Rooms:** Rooms are created on-the-fly the moment the first user opens a URL. Rooms are automatically destroyed when peers leave. No state is recorded in any database. 2. **Zero Storage:** Text chat messages reside exclusively in browser JavaScript heap memory and are wiped on tab close. 3. **No Intermediary Transcoding:** Video and audio are never decoded or transcoded on the server. 4. **Third-Party Immunity:** Because the signaling server only brokers SDP messages, server compromises cannot yield retrospective or real-time call audio or video. ## 6. Frequently Asked Questions (FAQ) **Q: Can 3 or more people use MeetSpace Talk together?** A: No. Multi-party group calling requires central SFU servers that collect and redistribute video, breaking direct P2P end-to-end privacy guarantees. MeetSpace Talk is strictly designed for 1-on-1 confidential communication. **Q: Does MeetSpace Talk store my name or IP address?** A: No. Display names exist only in the browser and in WebRTC DataChannel payloads sent directly to your partner. No IP addresses or logs are written to disk. **Q: What happens if someone tries to guess our room name?** A: Once both participants are connected, the room is locked. Any third person attempting to join is immediately blocked at the signaling server and denied access. For maximum security, use the built-in random room generator or choose a unique room name. **Q: How can I integrate or link to MeetSpace Talk?** A: You can generate direct call links with the format: https://talk.meetspace.me/call?room=YOUR_ROOM. --- ## 7. Official Endpoints & Verification - **Homepage:** https://talk.meetspace.me/ - **Call UI:** https://talk.meetspace.me/call - **Peer API:** https://talk.meetspace.me/api/room/:room/peers - **Health:** https://talk.meetspace.me/health - **LLM Summary:** https://talk.meetspace.me/llms.txt - **LLM Full Specs:** https://talk.meetspace.me/llms-full.txt - **Robots Policy:** https://talk.meetspace.me/robots.txt - **Sitemap:** https://talk.meetspace.me/sitemap.xml