After three intense months of work from more than a dozen contributors, #deltachat 2.48 releases are rolling. Maybe the most feature-packed releases ever?
- "zero metadata" messaging
- native Audio/Video calls on Android and iOS, as well as UbuntuTouch
- Group and Channel descriptions
- A new background audio player
- Revamped Download-on-Demand
and, last but not least, the long-awaited next-generation of messaging resiliency through "multi-path" routing ....
Delta Chat: Zero metadata, group descriptions, native audio/video calls and much more!
With the latest 2.48+ releases, a chat message reveals close to zero metadata to servers. For cryptographers and messenger enthusiasts, here are the key points on how we turned email very close to ...delta.chat

Luc
in reply to Delta Chat • • •Götz Hoffart
in reply to Delta Chat • • •Delta Chat
in reply to Götz Hoffart • • •Delta Chat
in reply to Götz Hoffart • • •zivi
in reply to Delta Chat • • •Delta Chat
in reply to zivi • • •Kenny
in reply to Delta Chat • • •zivi
in reply to Kenny • • •zivi
in reply to zivi • • •Kenny
in reply to zivi • • •That's not the issue here. For example, the blog post mentions multiple relays, but only one seems to be used for sending, which feels like that meme of a miner giving up right before reaching diamonds. If Delta Chat would send each message from a random relay, the problem would pretty much be solved. Alas, I have a love-hate relationship with Delta Chat, and I often find the choices of the devs puzzling.
Delta Chat
in reply to Kenny • • •Delta Chat: Zero metadata, group descriptions, native audio/video calls and much more!
delta.chatdexternemrod
in reply to Delta Chat • • •@kbruen @zaire
I like the step-by-step approach.
As soon as address-randomization is reached, the next complaint is that only the same n-adresses are in the pool. So the next request is to let DC create its own addresses. Get me right: This would be an awesome feature, I just use this to demonstrate that this is the nature of iterative approaches and ongoing improvements.
Séverin Lemaignan
in reply to Delta Chat • • •Delta Chat
in reply to Séverin Lemaignan • • •OnkelBobbyWhite
in reply to Delta Chat • • •Kevin_Runforrest
in reply to Delta Chat • • •jaseg
in reply to Delta Chat • • •Delta Chat
in reply to jaseg • • •jaseg
in reply to Delta Chat • • •thanks for the clarification. speaking from my network security background, the whole timing leakage is what i’d call metadata and what your “zero metadata” thing is protecting (AFAIU timestamps and cryptographic identities) in a cryptographic protocol i’d consider straight up data, not metadata.
thinking about an average user of a secure comms tool, i’d expect they would be surprised to learn that something that is “zero metadata” still leaks timing and through correlation identities.
Delta Chat
in reply to jaseg • • •If you want to discuss this further, it's maybe better done in a support forum post.
jaseg
in reply to Delta Chat • • •Vint Prox
in reply to Delta Chat • • •d1
in reply to Delta Chat • • •Blue Luma
in reply to Delta Chat • • •⁉️
in reply to Delta Chat • • •Is telephony e2ee? You only mention peer-to-peer and no mention of e2ee.
Well done, you guys are really advancing at a rapid pace!
And please no contact-discovery!
Delta Chat
in reply to ⁉️ • • •Delta Chat
in reply to ⁉️ • • •