Zum Inhalt der Seite gehen


A main technical and economic difference to #matrix servers/clients:
The family of #deltachat apps uses #chatmail servers as ephemeral message transports that know nothing and forget everything: Servers don't store group metadata or cryptographic identities and delete messages after download by default. In effect, a 30EUR/month #chatmail server with 10K's of active users hums along with 2% IO and CPU pressure, 1GB RAM and negligible disk usage. No Pro-version or Kubernetes needed to scale ;)
Dieser Beitrag wurde bearbeitet. (2 Monate her)
just to know, what would you say is the average hardware specs you'll need for an instance of 100-150 active chatmail users?
the cheapest you can get should suffice. SSD disc is always good but even without should be fine. A friend runs it on a raspberry pi for a housing project.
if this service scale, how can we prevent SPAM accounts?
By not having a central directory of users which you can search to spam them :) Delta Chat addresses are typically not public in any way, contact is initiated by invite links or by scanning a QR code in person.
Shorter description is,
delta chat keeps all social concepts (and metadata) on app level of protocol stack, not on transport's one, i.e. smtp.
Hence servers/service providers can know less.
Is there a way to back fill a local history on a new device from another one?
if you use the "add second device" action in settings al history and keys and messages and media files will be replicated to the second device ... You can then even kill the source device app and the second device will function fine.
That's great! Is it being done over smtp/imap as well?
no replication is streamed via local wifi with an Iroh P2P connection