Blog sketches a federated text messenger with end-to-end encryption
Original title: How to Create Your Own Decentralized Messenger Protocol
Peers would discover lnchat via /.well-known/lnchat.json and resolve recipient public keys before sending.
A Hacker News post walks through designing a small federated messenger, using email-style federation as the model. Identities are nickname@domain, servers publish protocol metadata, and clients keep private keys so servers see only ciphertext. The draft drops attachments, groups, multi-device support, and read receipts. It also notes a malicious server could publish a false public key unless users verify keys.
- Discovery file is GET /.well-known/lnchat.json with protocol lnchat.federation.v1.
- resolve_users returns current public encryption keys for local users.
- Private keys must not be sent to the server in plaintext.
- Suggested checks include fingerprints, TOFU, or key transparency.
From the original article
13 min read at karboosx.net
Let's say you want to create a system where each server can "join" a network and start exchanging something with other members within that network. How would you approach such a task? You could create a small centralized orchestrator that will accept join requests and handle that for the recipients, but that's not decentralized.
By fagnerbrack · karboosx.net
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.