 With our #deltachat #chatmail and #webxdc efforts we put all intelligence on the end devices, and architecutally separate it from a transport layer that routes safely and fast but knows nothing. There are a dozen or more #chatmail servers across many jurisdictions, all safely interopable with each other and classic servers. Turned out we can dumb down email servers by relying on cryptography instead of IP reputation and ai/spam filtering. And have 200ms delivery times. We are not done :) 14 comments
 Let's admit that's the case, then at the very least a disclaimer on the win download, and a warning when you are communicating with a windows client. Don't get me wrong, I love and rely on delta, but in the age of copilot AI, constant screenshots etc. that's a real problem, it can't just be brushed away. Perhaps don't drop the client, but ffs warn people. The illusion of safety is more dangerous than it's lack. SIgnal, Delta and others should at the very least put on disclaimers.  Runs very well on a Raspberry Pi Zero 2 with 40°C and less then 1 Watt over mobile-internet. No other concept do so.  @delta Delta chat is a very good messenger. I love it. The only drawback I have compared to xmpp messengers is that it does not support audio and video calls. I know this is difficult with emails, but if somehow you could make a calling sound when somebody calls to a jitsi video meeting ID that is already registered with Delta chat account. @madsee34583 there already is jitsi integration if you configure a base url in advanced settings but indeed no calling sound / ring yet when you receive a call invitation. And thanks for the positive feedback, much appreciated! |
Gregory's Server
Great, but (hot take incoming) you should still eol your windows client. e2e services make no sense in the age of copilot surveillance.
Sure a *nix or android end device is easily compromised, but windows is by default.
All serious e2e IMs shoud drop microsoft support and publicly explain why.
@delta