Experiments · field note

What a messaging prototype can teach

A brief look at client-side encryption, a WebSocket relay, and the difference between learning and shipping securely.

Keep the relay's role small

In an end-to-end encrypted messaging design, the interesting boundary is between the endpoints and the service passing messages along. The clients handle the cryptographic work; the relay is intended to transport ciphertext rather than read the conversation.

The Signal-style E2E Chat repository is an educational experiment built with TypeScript, Node.js, WebSockets and libsignal. It makes that separation concrete enough to study through code.

A prototype does not establish security

Using a respected cryptographic library is not the same as having a production-ready secure messenger. Authentication, key verification, device lifecycle, backups, metadata exposure, deployment, error handling and independent review all matter.

For this reason the project is presented plainly as a prototype. Its value is in exploring the shape of a system and the questions it raises, not claiming an independent security audit.

Read the code with its limitations in mind

The repository is the best place to inspect how the experiment is put together. Any production security claim would require a separate level of design, testing and verification.

EXPLORE THE SOURCE

The connected project page includes the implementation overview, available demo and code links, and limitations.

See the project ↗
← all writing