Ethereum

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

for Comm's launch, we had to cut scope and ended up launching without a backup feature

we're working on getting a v0 of encrypted backup out ASAP, initially centralized

that said our medium-term goal is to build out something decentralized and sovereign

what's the current best practice for portable, decentralized backup of user content in an ETH dapp?

attaching a schematic of the centralized v0 for context

for Comm's launch, we had to cut scope and ended up launching without a backup feature

we're working on getting a v0 of encrypted backup out ASAP, initially centralized

that said our medium-term goal is to build out something decentralized and sovereign

what's the current best practice for portable, decentralized backup of user content in an ETH dapp?

attaching a schematic of the centralized v0 for context

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

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

What you’ll most likely eventually land on is encrypting the backup key and then storing on the users Secure Enclave (iCloud). There isn’t a more secure “consumer friendly” method than this that I know of, but you could also go one step further and generate @safe for each user and then co sign, but I don’t think that’s needed for messaging.