Other interesting problem to solve for mail clients is the editor. You should be able to forward/edit untrusted html content. Source: I develop tecotype.com for mac/linux/windows.
One good alternative is AppImage. Works on every distro out of the box, but doesn’t have the permission system of Flatpak.
For example, I'm using catch-all address with fastmail. I wasn't able to find any client with the right design that would allow me to define sender address and email account separately during composing, so I can use "alias@test.com via me@example.com" as a sender.
You can send "ping me when linux available" and I'll follow up.
If I can be a beggar and a chooser: The vim keystrokes to go to the top or bottom of the current email list and/or the conversation thread items are sorely missed.
I did that in my IUP fork, bold, italic, headings, link, image, table, that can all be mapped to native text widget, can load and save markdown from that.Will it look as intended, no, but, do not create websites when you send emails and everything will be fine.
Should be TUI-based and for Linux + Mac.
They argue that just as programmers once wrote ASM and C, the arrival of Java and Python meant you no longer had to be a neckbearded autistic kid to write software that doesn't leak memory or segfault.
Arguments like this show me you’ve never done software engineering seriously.
Despite compilers (written by some of the smartest engineers on Earth) trying hard to prevent developers from writing shitty software, those new age "engineers" still managed to ship software that crashes, leaks, and generally sucks.
I'm not saying this email client is not secure (although I'd bet 5$, it is). But it seems beyond silly to assume software is automatically safe just because a new piece of tech can potentially find vulnerabilities. Intent still matters. And the 99% would never have the intent to write secure software.
Hard agree, especially the apparent 99% of AI boosters on HN who seem to basically only care about shipping arbitrary products as fast as possible and skipping the whole middle part where someone sweaty person is grinding through the details intimately, all day, and while they should be sleeping.
At my last place, it was a battle to convince the narcissistic idiot CTO and even one of our senior engineers (both in age and experience) that it was important to encrypt customer data before it transited through third-party cloud service providers. People don't—and aren't incentivized—to give the slightest shit about quality, security, you name it.
This normally happens on two scenarios: a) they are not paid enough to care that much or b) they are paid more than enough to not have to care that much.
Either way it’s almost always down to how much the company is willing to pay for people that actually care about these things.
… but as shown by many shovel sellers… their shovel…
Here I fixed it.