If they keep this shit up, plenty of people will be taking the step to turning them into a historical footnote. Expecting the service you’ve paid for, without interruption, is not a difficult ask.

Except apparently for Proton, it is.

If only there were a way to pilot changes through a tier of users willing to act as testers.

Last I checked, the former was still an issue.

The latter, I have not tried because its easier to just use OVPN and avoid thd app and its potential issues. Regardless, Proton left paying clients with two fundamentally broken apps for months to years.

Edit: The issues with the mail client persist.

Hopefully they fix it faster than the “email from the mobile app sends before saving the last live copy, truncating the email” issue they’ve been having for nearly a year and the “installing the VPN client on Linux will utterly break non-VPN connections” that has been plaguing Linux users since at least 2021.

I was an early adopter of Proton. Their new attitude of “features, not fixes” has me looking elsewhere.

It is when it does not seem to solve the issue. We will try it again.

I may try that, but the old one being critically broken for years is a terrrivld look.

If I can find one, I may do. At this point, self-hosting is appealing, though I don’t particularly care to fight with Google etc over erroneous blacklisting and such.

Between this and their “broken since at least 2021” Linux VPN client issues, I am questioning why I drop $30 a month to support them.

Regardless, Proton acknowledges the issue:

Please be informed that the issue has been reported and our developers are aware, they are look for fixing it in one of the future updates of the app. Unfortunately, we cannot provide an ETA on when the permanent fix will be available.

Not exactly a stellar reply, given that their business revolves around their email offering.

We did try the beta app, a few times. Generally we notice it on the other end; the recipient (especially one external to Proton) gets a truncatesd message or rarely, an empty one. I am 90% certain it has to do with the way Proton saves drafts before sending; I’d bet that it is not verifying the displayed version (user’s version) against the last draft.

I mean the email. Apparently it is a known issue for some people on the Android client. I tend not to use the client to send, but my partner does regularly. Out of every three messages, at least one is missing data at the end of the message. It does not seem to be device specific.

Might do, but we’ve tried that before. Its a bit oof for an app trying to compete with enterprise tools. I’d much rather see email work flawlessly v. adding drive etc.

Yes, they offered that up to us too. We might just have to migrate off of Proton and onto Tuta.