Expected behavior
My user story would be:
I download the files intended to run deltachat
I serve it in a URL like https://chat.example.org
I run it with my firefox profile for communications, and I pin tab it
Actual behavior
Looks like it is mandatory to run deltachat-desktop (which might contain an HTTP server). Hence, I am stuck in step one: how to download the intended files to be served in a boring HTTP server? Is it documented?
References (what do others)
matrix: yes
I am aware that element matrix client , allows being used through desktop, but also web:
whatsapp, telegram: yes
They allow web usage (please, here it is out of scope about the “linked device with a QR” feature):
signal: no
signal does not allow to be used outside of its own client, that’s why I don’t use it
1 Like
9er
October 9, 2025, 11:26am
2
AFAIK for http server be trully boring you need to rewrite GitHub - chatmail/core: Chatmail Rust Core library, used by Android/iOS/desktop apps, bindings and bots đź“§ in JScript, or otherwise make is functioning in the web browser. Then you need to adapt a GUI (maybe from Electron desktop DC app).
But maybe Rust core can be runnng on (not so boring) (trusted) server, and web GUI will connect to it…
1 Like
WofWca
October 10, 2025, 5:30pm
3
Running Delta Chat purely in the browser (as a static HTTP site) is currently impossible, because browsers can’t make IMAP / SMTP connections. See
We recently made a web version of the delta chat desktop UI. (blog post: Delta Chat Desktop, but running inside of Firefox - Delta Chat )
The downside to this is, that it still needs a local server component to run chatmail core (formely known as deltachat-core-rust).
Ideally we would be able to not need to this server component and run delta chat as fully standalone web app or browser plugin.
Our core library is written in rust and rust a popular source language for compiling to webassembly…
There is a way to run it as a non-static website though, but it’s not intended for production (probably not secure):
2 Likes