Sodfa Chat — Decentralised P2P Messaging
Pairing and messages travel peer to peer; nothing is stored on a central server.
Project Summary
A decentralised (P2P) random-chat platform that connects two users directly, so messages travel between them through a transport-and-pairing broker only and the conversation is never stored on a central server. The experience includes dark mode, full message management and interface effects.
The Problem
Classic random-chat platforms store everything on a central server: conversations, pairings and metadata. Privacy therefore remains a promise in a policy rather than a property of the architecture — and liability for any potential breach sits entirely with the server.
Sodfa Chat inverts that assumption at the root: pairing and message content travel between the users directly (P2P), and the broker handles transport and pairing only, retaining no conversation content.
Key Features
Direct peer pairing
A random room establishes a direct channel between the two sides instead of routing content through the server.
Transport-only broker
The server knows who is online right now and facilitates pairing; it never retains the conversation.
Full message management
A familiar experience: send state, deleting a message, and retry on failure.
Dark mode & effects
The interface supports both themes and respects the system reduced-motion setting.
Fallback for restricted networks
When a direct connection fails the system moves to a fallback path instead of reporting "offline".
Technical Challenges & Design Decisions
- Pairing two strangers: a random room needs a broker that knows who is online now and links the two sides. That broker is the minimum necessary — everything after it travels peer to peer.
- Browser limits: WebRTC grants a direct connection but fails behind networks that block peer-to-peer traffic. The fix was a fallback path rather than turning that failure into an error message for the user.
- Keeping the experience simple: P2P systems usually lose one essential quality of ordinary chat apps — simplicity. Message management, dark mode and effects were added so the experience stays familiar rather than experimental.
- Explicit boundaries: the tool shows the user what leaves their device and what passes through the broker, so the privacy decision is not left to an assumption.
Technical Architecture
- Signaling path: exchanging initial connection information between the two peers — no conversation content.
- Data channel: messages travel directly between the peers once pairing succeeds.
- Fallback path: invoked automatically when the direct connection fails, while the broker still stores no messages.
Testing Methodology
- Tested connections across several networks, including those that block peer-to-peer traffic, to confirm the fallback path works smoothly.
- Verified that no conversation content remains on the broker after a session ends.
- Tested pairing under load (several concurrent users) to confirm system stability.
- Reviewed the interface across screen sizes and in both light and dark themes.
- Reviewed accessibility: keyboard navigation order, focus states and reduced-motion support.
Outcome & Impact
- No central storage of message content on the server — minimal knowledge held by the broker.
- Immediate pairing with an explicit network-failure path instead of an error message.
- A familiar experience (dark mode, message management) built on a decentralised architecture.
The project is open source. To report a vulnerability see the responsible disclosure policy, which commits to a 72-hour acknowledgement.