Search

Items tagged with: ChatMail


@kbruen well I guess that is a matter of opinion? because this other person is saying totally the opposite:

mastodont.cat/@spla/1156953525…

and besides that, setup is something you do only once, the real struggle comes next, I have never self-hosted matrix but see people complaining or even de-federating due to server burden, while I do host a #chatmail server with +8k users in a 5eur VPS using 1.2gb of ram and 19gb of disk, now try the same with #matrix

I am total noob self-hoster btw

@delta



in speaking with my colleagues at @delta i began to test multi-transport (multi-relay) functionality.

early testing looks very good on android, just now we wait until all client engineers bring core library into parity.

we are close to being unstoppable.

now is an amazing time to try #deltachat

interested in running #chatmail relay?

chatmail.at/ github.com/chatmail/relay

or contact me. i run several and am happy to help you onboard!


RE: chaos.social/@thefinalstrawrad…

Another nice surprise! A careful discussion and appreciation of our almost 8-year long running efforts, and its #deltachat and #chatmail artifacts. The "Signal contingency plan" comes complete with podcast, website and zine!


@sarae state actors could run #chatmail servers, and maybe that is happening today. But the server does not get private data, and can not break the end-to-end encryption, and so does not see any metadata like profile names, avatars, group memberships etc.


#Telegram has a nice and fast UI, granted.

But the 1 billion people using TG are at risk because of its big central database that any state security service craves for. Moreover, several anonymization proxy-bot offerings were hacked in 2024, identifying millions of users and content.

#deltachat builds anonymization directly into the app and has pervasive end-to-end encryption. #chatmail relay operators can sleep well, knowing they have nothing. Ergo, E2EE is good for any operators sleep! :)


if you use #DeltaChat or #ArcaneChat, I recommend you to use them with #chatmail accounts, which provide faster speed and prevent spammers/scammers from sending emails to your kids and other family members, only other family members will be able to get in contact with them via QR scan or invite link


#chatmail does secure email federation that works. Using lean "relay" servers that enforce metadata-minimized end-to-end encryption.

There is a new little tool that checks whether two relays are interacting well for messaging, and how fast. You need a terminal window and be able to execute:

pip install cmping

you can then run for example:

cmping mailchat.pl nine.testrun.org

to perform a "ping" test for e2ee-messaging. Also see chatmail.at/relays

github.com/chatmail/cmping/


@arale_xan This is not about a full technical comparison of security aspects. Our post was more about UX goals here in this thread. That being said, email metadata in #chatmail messaging is pretty minimal, and we are working on reducing it further: delta.chat/en/help#message-met…


The #chatmail #rust core is the base infrastructure library used by all apps and bots. It contains all networking, encryption, email processing and implements all the relevant IETF email standards. It's a single central development place with which the whole ecosystem of clients and bots can upgrade consistently.

We are constantly trying to remove code, and to cleanup things. That's a must to keep a 8-year long evolved code base agile and adaptable. Key insight: The best code is no code ;)


that single dev was actually supported by mainline #chatmail relay developers along the way, and besides, the Go-efforts (there are two) are not production ready yet.


Any data that is collected on servers will eventually leak or be abused otherwise.

By design, no one can enumerate #deltachat profiles which are private and not published on any server. Conversely, #chatmail relays do not see or collect private data or metadata.

But wait, there is more :)

We are currently evolving end-to-end security protocols and UX to **survive an attacker fully taking over a server**. The attacker shall not even be able to message users, let alone impersonate anyone.


While #cloudflare US-east1 is busy fixing a good part of the Internet, parts of Matrix/Element, X etc down, good old decentralized #chatmail continues unimpeded and without degradation :)

In other news, there is a new #freebsd community maintained ❤️ #deltachat desktop install:

pkg install deltachat-desktop

thanks @feld and others!


#chatmail might be a new way to deliver email but it's not a new way to deliver mail :)

"Poste restante" or "general delivery" or "waiting mail" is a mode where one can send a message to a name or, in some countries, pseudonym, @ a post office address and then someone else can come and get it, showing their name or pseudonym (passphrase). en.wikipedia.org/wiki/Poste_re…

Curious, which of you know/have used the poste restante mode of delivering postal mail at one point in your life?

  • used "poste restante" delivery multiple times (6%, 14 votes)
  • Used poste restante once (3%, 8 votes)
  • Heard of it but didn't use (27%, 65 votes)
  • Never heart of it. (62%, 146 votes)
233 voters. Poll end: 3 weeks ago


this is not your grandfather's twitter bootstrap framework.

finalizing design for #deltachat #chatmail system. by hackers for hackers.


Denmark and other EU governments still pursue #chatcontrol.

They still want to permanently legalize client-side scanning but postponed making it mandatory.

They also want to increase age-verification controls which risk to ruin what little is left of privacy in current digital spaces, taken hostage already by US corps.

Ourselves? We double down on providing the most private, reliable and fun messaging experience, with a growing federating #chatmail relay network across the globe.


#deltachat is a private messaging app. It'd be easy enough to offer various public groups to boost onboarding, and let everyone play. But one would land in a large group that isn't very private, with lots of needs for moderation tooling, troll handling and other social-media issues. Not our current cup of tea.

We are grateful for the many folks here onboarding their families, projects or friends, founding special-interest chats, setting up #chatmail relays etc. This is wonderful, cheers!


i love the #chatmail tag as it makes the technology immediately comfortable for the less tech savvy. But a little searching shows that ChatMail is a registered trademark of Myntex, Inc (whoever that is?). Are these related? Is there hope for us to be able to use the chatmail name/tag/label?


Many experts caught up in the past crypto/decentralization discourse fail to recognize one key innovation area of #deltachat and #chatmail efforts:

A user interface (UI) and experience (UX) that mimicks and closely resembles Whatsapp and Telegram ... who both have a central cleartext database of identities, social graphs and, in the case of Telegram, also messages and media, of billions of users!

We prefer to ground every discussion in UX/UI terms and measure security by outcomes for users.


@vort3 you have a point and it's kind of funny that even though #chatmail uses the email system, one can't just give out an email address. The challenge is to establish automatic end-to-end encryption while maintaining identity privacy (in Delta Chat we want chat profiles to be fully private and decentralized so can't just do some central registry). There are some ideas on how to bring back the ease of telling your address and people contacting you. Just more involved than it sounds :)


@lexinova @upofadown FWIW there are some non-electron clients chatmail.at/clients and an upcoming post about an experimental Tauri one. The current #deltachat desktop electron-based client tries to both size-bloat/ram wise do better, and also e.g. bars the frontend rendering process from doing any Internet connections which are purely done via the Rust core library, for all #chatmail clients.


we hear you but it's the truth: by onboarding to #deltachat today you are diving into an experimental testrun of "the future of email" , also known as #chatmail chatmail.at

Finally we, as app distributors, want to fully disentangle from any "default" server. Testrun will become history :)


1) there are bridges ("matterdelta") which provide interop with Matrix, XMPP, Telegrram, ssh and anything that Matterbridge provides. It doesn't preserve end-to-end encryption and so bridging bot choice is tricky.

2) There are growing efforts around 3rd party #chatmail clients chatmail.at/clients. Interoperability is "free" between all chatmail clients (#deltachat being the prominent one). Unlike #Signal we welcome third parties to the party :)


there is also a tauri version, we will publish the blogpost about that somewhere in the future. github.com/deltachat/deltachat…
Also this browser version is not standalone, it still requires one server instance per user that runs deltachat/chatmail core. Ideally it would be just a PWA, but for that #chatmail core needs to be compiled to, and work in wasm: support.delta.chat/t/what-woul…


Abrimos un canal de Puerto Rico en Deltachat para probar las aplicaciones.

Si estás en boriken.social, aparecerá el enlace en un anuncio arriba.

Si no lo estás, escribeme un DM y te invito.

#PuertoRico #BorikenSocial #MastodonPR #Deltachat #chatmail


most chatmail relays have higher quotas (usually 200MB or more). #Chatmail relays remove messages unconditionally so the quota is not comparable with classic email servers which tend to keep messages forever.
The "100MB" is an early default and it should be increased to better match current standard practises.


@tomli what does IP address hiding have to do with the topic of the post? :) Anyway, Cloudfare probably sees all signal group members by the access pattern to in-chat media, including their IP address. Each #chatmail relay only sees IP addresses of its users but not of users of other relays.


Signal's president claimed it takes billions to replicate the availability and reliability of "hyperscalers" (AWS/Google/Microsoft/Cloudfare) that Signal uses.

#chatmail and #deltachat are about disproving this claim by

1) making relays super cheap (DONE)

2) enabling chat profiles to use multiple relays redundantly (WIP)

3) distributing relay knowledge among chatters (TBD).

Fat servers, corporate overlords and billionaires: not needed and better to not exist for a convivial e2ee future :)


quick heads up. Our impressions: #matrix is going strong with public sector entities, and it's where most dynamics happened at the conf.

We are rather focused on private and resilient messaging where servers don't play a big role; as we want #chatmail relays to be dirt cheap to operate, no pro version needed. Our focus is on informal usage, groups, family, friends, affinity or interest groups, whereas matrix is increasingly focusing on corporate/ organizational use cases. YMMV


Our project is one of constant exit planning and circumvention considerations ... as times and tech are getting more shitty.

We don't bet on a single basket, and not a single state or jurisdiction, and certainly not AWS/Google/Microsoft US clouds which run #Signal servers.

No single hoster, platform or language (we do a lot of Rust, granted) and no single device or vendor. At #chatmail protocol levels we regard nothing as holy, and look for simplicity and robustness, and convivial community 🖤


Believe it or not: #deltachat is growing audio/video calls starting with the currently rolling 2.22 releases ... A few people already had two hour long stable calls :)

Calls are an experimental option while we continue to work on reliability, UX/UI revisions, and configuration of TURN servers on #chatmail relays and in clients.

We want calls to reliably work across all major platforms, networks and phones, including #UbuntuTouch

Feedback and debugging happens at support.delta.chat/t/help-test…


Good news! It's getting harder to keep track of new #chatmail relays :)

Recently several public relays were added to the chatmail.at/relays list, in Warsaw, Helsinki, Romania and Barcelona.🧡

If you have #deltachat installed on mobile, you can go to any chatmail relay website in the list and click on a link there to create a chat profile.

It's wonderful to hear about collectives setting up chat infrastructure like the recent xat.fedi.cat from @fedicat and @eXOfasia


I've been on the hunt for some accessible, easily self-hosted (on prem or datacenter) chat solution for a while now, and I've been looking very closely at deltachat/chatmail.

Not gonna lie, the fact that just uses mature SMTP facilities for transport is making me weirdly aroused.

If anyone has experience running their own chatmail server or just using deltachat in general, I'd be glad to hear from you.

#DeltaChat #ChatMail #SelfHosted #HomeLab


@michal don't underestimate your role :) you created one of the first #chatmail relays and kept it running ever since ... apart from the service to some hundreds of users this provides it also helped our motivations, and motivation is a key driver for any collective community-driven project :)


Not taking Venture Capital money means:

- No pressure to maximize monetization of usage (for every million of VC funding you need to find ~100+ Million in value later).

- No prioritization of growing fast with PR campaigns that promise the moon and stumble on the ground

- No billionaire who ultimately profits

Instead, we seek public funding and private contributions for #chatmail #deltachat and #webxdc developments.

Thanks to everyone who is helping and already test-driving things :)


There is no single central #Signal server. Signal uses #AWS cloud, plus Google Cloud, Microsoft Cloud and Cloudflare, all under US legislation. If any of these clouds goes down or becomes otherwise problematic, chatting degrades or fails.

With #deltachat you can choose #chatmail relays ( chatmail.at/relays ) which distributes the risk across a wider network. We are currently working on the multi-transport feature to finally remove any central point of chat failure chaos.social/@delta/1153621448…


The last 2-3 days there was a significant slow down with message sending, sometimes 15 seconds, via the default #chatmail relay .... Wasn't a CPU/RAM or other resource problem but a software configuration / implementation problem. After some hours of debugging it was solved by providing the "speed-adjust" proxy option to #postfix. message sending should be back to sub-second. No message was lost. Lesson learned: just search for "speed" in postfix docs first (and fix the offending module later).