Whisper - keith.is
End-to-end encrypted P2P chat using Iroh and Bluesky identity. No servers, no logs. Your ATProto DID is your address book, Iroh handles the rest.
Every Voice and Video Call on Discord Is Now End-to-End Encrypted
As of March 2026, E2EE is now enforced for every voice and video call on Discord. This represents a multi-year commitment, and Discord’s VP of Engineering is here to talk about why it matters.
I2P - The Invisible Internet Project | EN
I2P is a fully encrypted private network layer. Protect your online activity from surveillance and censorship with built-in end-to-end encryption.
An End-to-End Encrypted Peer-to-Peer Chat System with Self-Sovereign Identity
Today, messaging applications are the most popular medium of communication over the Internet. As their use has grown, different security and privacy concerns have received the attention of users. Users consider what they send with others to be private, tamper-proof and secure without getting exposed to unintended entities. Furthermore, users are concerned whether their data is exposed if the service provider encounters any cyber attack. In this paper, we propose a Self-Sovereign Identity (SSI)-based End-to-End Encrypted Peer-to-Peer (E2EE P2P) chat system that does not rely on any specific provider, enhancing user privacy and security. The system leverages decentralized identifiers (DIDs) to establish secure communication channels using the DIDcomm (DID Communications) protocol, which ensures the privacy of user data. We also introduce a secure file sharing mechanism that ensures that all data, including messages, are stored solely on the user's device, further safeguarding user privacy. The system is developed following the Design Science Methodology, addressing probable threats and satisfying different functional and security requirements. The architecture and its implementation details are discussed with the subsequent use cases and protocol flow. Finally, we analyze different aspects of the system.
Licensing needs for Truly P2P Software
This article is preserved for historical purposes but HAS BEEN SUPERSEDED BY THE CRYPTOGRAPHIC AUTONOMY LICENSE.
Better Encrypted Group Chat
Broadly, an end-to-end encrypted messaging protocol is one that ensures that only the participants in a conversation, and no intermediate servers, routers, or relay systems, can read and write messages. An end-to-end encrypted group messaging protocol is one that ensures this for all participants in a conversation of three or more people. End-to-end encrypted group […]
Is End-to-End Encryption Optional For Large Groups? - Dhole Moments
One of the recent topics in Messaging App Discourse is whether it makes sense to prioritize End-to-End Encryption (E2EE) when searching for an alternative to Discord. Who’s Saying “No&#…
The Long Tail of Work Left Until ActivityPub Has E2EE - Dhole Moments
Separate from my proposal for key transparency for the Fediverse (which I’ve certainly blogged about a lot), the W3C has been working on building out end-to-end encryption (E2EE) for Activity…
How to Use Signal Encrypted Messaging
The best end-to-end encrypted messaging app has a host of security features. Here are the ones you should care about.
Wave - Secure Messaging App
Privacy-first messaging with quantum-level encryption. No signup, fully decentralized, zero tracking.
Investigation into Message Layer Security (MLS)
This article investigates Message Layer Security (MLS), the IETF standard protocol (RFC 9420) for Signal-style end-to-end encryption. Through a practical analysis of OpenMLS (the Rust reference implementation) and a demonstration CLI chat application (mls-chat), the post reveals the substantial gap between protocol specification and production deployment. Introduction MLS (Message Layer …
Riot releases end-to-end encryption: get ready to chat securely!
Today is a big day in the Riot world, finally releasing the very first cross-platform implementation of Matrix’s end-to-end encryption!
if atproto adds E2EE messaging support, will be a bunch of questions: would it be integrated directly in client apps (like Bluesky), or be a separate client app experience? would you have per-app chats (for content sharing), or account-level (generic msgs w/ DIDs)? if the later, why not just Germ?
