DevTrends开发者趋势
主题色

emn4tor /

seal

Hey y'all, I've built a completely free open-source p2p Messanger in my free-time. Most 'private' messengers still rely on central server infrastructure to queue and hold messages in an inbox - that m…

DT数据与运维DT内容 / 资源

关于

Hey y'all, I've built a completely free open-source p2p Messanger in my free-time. Most 'private' messengers still rely on central server infrastructure to queue and hold messages in an inbox - that makes it a target for metadata or message collection. With Seal there is NO Server-Side Inbox: Every Message directly travels from peer to peer via libp2p. Every Message is 'sealed' using Olm (1:1) and Megolm for groups via vodozemac The only server needed is a directory server, which purely acts asa short-lived adress lookup table The Architecture is interesting too, your chat identity is an Ed25519/Curve25519 keypair generated locally, your public ID is simply the key fingerprint. I'd love to hear your thoughts on the project. I used Claude to help draft the initial code comments explaining the reasoning behind key architectural decisions, but I manually reviewed, audited, and corrected every single comment.

收录记录

  1. Show HN

    2026年8月11日 · 1 次收录

讨论这个产品