Skip to content
NewA calmer, faster ZeroHour

Blog sketches a federated text messenger with end-to-end encryption

Original title: How to Create Your Own Decentralized Messenger Protocol

Hacker News · securityby fagnerbrack ()13 min read1
AI summary · x-ai/grok-4.7Summaries by Vani AI

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.

Key facts
  • 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.
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

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.

Hacker News · security

By fagnerbrack · karboosx.net

Read the full article at Hacker News · security

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.