From Bouncepaw’s links:

On inboxes as application-specific todo lists.

d6 wrote.

signal-cli has been around for a long time and is pretty established and trustworthy (in my opinion). as long as

Modern email server that integrates all the new email protocols like dmarc. I haven’t tried it personally.

link2xt on Delta Chat’s forums.

Problem with OAuth 2 is that it requires pre-registering Delta Chat with each email provider and hardcording OAuth 2 authentication URLs into the application. This option is limited to large providers and they can always decide to change requirements and unregister the client.

Here’s a rival project also trying to make an SMTP/XMPP gateway.

Fun!

Fett!👍🏻 Autocrypt support is planned.

Here’s the open tickets for that.

There’s also an ActivityPub gateway already.

Seems like Libervia is working on an email ⇔ XMPP gateway.

Jag håller med om att Delta Chat som bygger på en etablerad standard kan vara ett sätt att frigöra sig från den gisslansituation som annars råder, men rent funktionsmässigt blir det inte en ersättare för chattar eftersom den bara ändrar på den egna sidan av kommunikationsutbytet.

Men det är ju det här som inte stämmer för båda sidorna kan ju använda Delta Chat. Så om baseline är WhatsApp, Signal, Discord, Line, WeChat, Facebook Messenger, ICQ, AIM och liknande gegga, så uppfyller ju Delta Chat det, dvs att det blir en tjatt om båda installerar.

Och vad som dessutom går är att starta tjattar med folk som faktiskt har mejlappar som dom kollar lite oftare eller där du är OK med att dom bara svarar en gång i månaden. “Dessutom”, alltså, inte “istället”. Och alla som är på internet kommer behöva ha en mejladdress för det behövs för typ password resets och sånt.

Oh, great, there’s an RFC, that’s awesome.

Maybe Gmail will just switch to that and no milters will be necessary?

I already started a thread.

App idea.

Postfix milters that translate Gmail’s dumb reaction format to Delta Chat’s good one, and the other way around. Would only work on the unencrypted threads with Gmail users so the benefit is pretty minor.

I’ve found specs for how the reaction looks on Gmail’s end:

Interesting compromise.

FairEmail will send the Autocrypt header for use by other email clients, but only for signed and encrypted messages because too many email servers have problems with the often long Autocrypt header.

Comments like this…

I’m not exactly in a position to convince them to use tuta, so openpgp is required for me.

Google.

To use Postmaster Tools, you need to have a Google Account

Isn’t that kinda fucked up?! The whole point of running an email server is to not have to have a Google Account!

I scolded @smorkin for sending markdown emails but it turned out that it was Delta Chat that was converting his HTML-only emails to markdown (kinda uglily but that’s on me, I need to send a patch if I’m not happy, main point is that the behavior was on the receiver end).

So the scolding shifted to be about sending HTML-only emails in the first place 👩🏻‍🏫

Why my Dovecot! I loveded you! I loveded youuu!

Is there a fork on the horizon?

I finally cooked up a workflow so I can handle huge threads in the Emacs frontend for Notmuch seamlessly:

Patchwork might be something to keep in mind as an opportunity to install later on if I get overwhelmed by patches. Right now it’d be a complete YAGNI. Also it’s Django.

I like the idea: it doesn’t intrude with the mailing list workflow at all, it’s just an extra “view” of the patches.

Why interop with Proton matters even if Proton is a li’l sus: