Founders

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

probably my biggest weakness as a founder is that I'm a perfectionist.

it took me 8 years of building before I felt comfortable launching Comm. the hardest part was coming to terms with the scope we had to cut.

we're launching today without backup and without self-hosted keyservers, two critical features (coming soon tho!)

every founder knows that done is better than perfect. but for me, if the product I'm launching doesn't reach my own personal bar, I have a really hard time feeling comfortable with it

how do other perfectionist founders handle this stuff? maybe we need a support group lol

probably my biggest weakness as a founder is that I'm a perfectionist.

it took me 8 years of building before I felt comfortable launching Comm. the hardest part was coming to terms with the scope we had to cut.

we're launching today without backup and without self-hosted keyservers, two critical features (coming soon tho!)

every founder knows that done is better than perfect. but for me, if the product I'm launching doesn't reach my own personal bar, I have a really hard time feeling comfortable with it

how do other perfectionist founders handle this stuff? maybe we need a support group lol

https://warpcast.com/ashoat.eth/0x427722f7

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

Seek feedback and prioritize key features. Remember perfection is subjective. Join a community of like-minded founders for support. Launch and iterate