Reminder: There are no accounts in the classic sense anywhere with #chatmail or #deltachat.
It's all private profiles on end user devices which co-ordinate in a #p2p fashion. Chat profiles *use* email (relay) addresses for transporting messages through a federated e2ee-restricted SMTP network.
A chat profile or chat group has zero data on the server. It's radically different from classic email servers, Whatsapp, Signal, XMPP and Matrix servers which host and control chat identity.
This entry was edited (3 weeks ago)
Delta Chat reshared this.
Ketakater
in reply to Delta Chat • • •I really like the concept but have zero energy to convince my peers to switch to a new platform/technology
Maybe some day
hidikem
in reply to Delta Chat • • •one feature that could be nice it's a sort of feedback on witch user know witch relay.
When we change relay we don't really have a proper feedback on witch user know us on witch relay (so it's more difficult to decide when we can remove a relay).
roughnecks
in reply to Delta Chat • • •Delta Chat
in reply to roughnecks • • •roughnecks
in reply to Delta Chat • • •Delta Chat
in reply to roughnecks • • •Tael 🔜 AC26
in reply to Delta Chat • • •A New Kind of Instant Messaging
Project ToxDelta Chat
in reply to Tael 🔜 AC26 • • •@tael
we can't offer a full comparison but here are three key points:
1. Tox is not a cross-platform user offering like #deltachat, but more an infrastructure library like github.com/chatmail/core
2. Tox can only transfer messages between contacts who are online at the same time. complicates mobile usage.
3. Tox depends on a global distributed hash table (DHT) to find other contacts; doesn't work in highly restricted networks like during national internet shutdowns/larger failures etc.
GitHub - chatmail/core: Chatmail Rust Core library, used by Android/iOS/desktop chatmail apps, bindings and bots 📧
GitHubAleksandr Koltsoff
in reply to Delta Chat • • •Is there a technical architectural document about the system somewhere? I've tried finding one already couple of times but search engines are not liking my queries for this.
A self-contained blog article would be also fine 🙂
Delta Chat
in reply to Aleksandr Koltsoff • • •Delta Chat Cosmos
cosmos.delta.chatAleksandr Koltsoff
in reply to Delta Chat • • •I think what would be helpful is a document that describes a "lifetime" of a single message and the systems and components that are involved in processing and forwarding it. Also for group communication.
There seems to exist separate documentation bits for individual things (like on cosmos) but I'm having trouble finding system level documents.
Kenneth Bousquet
in reply to Delta Chat • • •Diane
in reply to Delta Chat • • •I know of two difficult edge cases for p2p designs.
Can two people exchange messages if they are not online at the same time?
Can one person receive the same message on more than one device?
Delta Chat
in reply to Diane • • •@alienghic yes, and yes. that's what the smtp/email relay network is used for:
1. Peers don't need to be online at the same time at all. And multiple devices are consistently synchronized.
2. Each device is equal to other devices. If your first device dies, the second device will be just fine, and you can setup a another third from it.
eltheanine
in reply to Delta Chat • • •Delta Chat
in reply to eltheanine • • •Delta Chat: Zero metadata, group descriptions, native audio/video calls and much more!
delta.chat