Comm

introducing Comm, a new kind of messaging app. we extend Signal-style encryption with a federation layer

Comm supports two kinds of chats:
1. Signal-style E2EE group chats & DMs
2. chat communities hosted on federated keyservers (like a modern IRC)

where Discord is chaotic and messy, Comm communities are organized and built for async

we're using Farcaster to bootstrap not just our social graph, but also our interest graph. when you log in with Farcaster, we'll automatically add you to communities based on the channels you follow

check it out: https://comm.app/download

founder of @comm.eth
open source / build in public

does having own keyservers allow for custom clients using your own tech/tooling/sdk, or is it locked down?

✳︎ design engineer → @ponder 
✳︎ explorer of humanism • petrolhead/gearhead
✳︎ React/SwiftUI
✳︎ bento.me/matthew

nothing is locked down, but custom clients can be built with or without having your own keyserver

keyservers are part of the protocol in a similar way to Farcaster hubs, except we want average users to know them

whitepaper coming soon!

definitely not out of scope!

you're the third person to bring this up, so it's clearly something users want

it's not the easiest thing to incrementally build, but it's something we'll eventually need to properly compete with Discord

one more thing, do you see room in the future for group voice calls, or would this be out of scope for the core value proposition of the project?

i see a "replacement for discord", but one key ingredient everyone is forgetting is having SOLID voice chat with minimal lag and solving for talking over one another