Build Your Own Federated Messenger Protocol, Email-Style
How to Create Your Own Decentralized Messenger Protocol

A hands-on walkthrough for building a federated chat protocol called lnchat, modeled on how SMTP servers discover and talk to each other. It covers email-shaped identities like [email protected], discovery through a .well-known JSON file, server-to-server endpoints for resolving and publishing public keys, and end-to-end encryption using HPKE-style encapsulation. The author is candid about the limits: a compromised server can lie about keys, so real E2E needs fingerprints, TOFU, or key transparency.
If a server is responsible for publishing users' public keys, a malicious or compromised server could lie about a key.
- _spduchamp
Or use LXMF on Reticulum.
- vidarh
I find it funny that it starts with email and then proceed to dismiss it in favour of building a bunch of things from scratch.
I have used email as a decentralised messaging protocol for software.
It works just fine, and we got a lot for free, including queueing, retries, federated lookup etc.
And it made debugging so easy: Just Cc: messages, or send messages from your email client.
It underpinned part of the initial infrastructure for the demo registrar platform and the email forwarding for the .name top level domain.