Recent submissions

Comment · 1 year ago
I don't need another desktop app...

The only thing I miss is the official API for the scheduled sending feature.

That's the only thing I would open the webpage app to do.

Comment · 3 years ago
Comment · 3 years ago
Looks good. I hate how IOS does, especially with certificate pinning, so I cannot use my ad-block http mitmproxy to block ads in Apps.

EDIT: thanks for people clarifying that pinning is done by Apps and not by IOS.

Comment · 3 years ago
Open source does not magically make your software more secure. Community needs to audit the code if they are going to use it instead of trusting blindly.
Comment · 3 years ago
That's why we should isolate Chromium from Google. Chromium should be lead by third-party like W3C.
Comment · 3 years ago
Hard Pass for closed-source browser.
Comment · 3 years ago
Comment · 3 years ago
Code should be self-documented. And editor should have a good mechanism to help you understand the source code. Emacs does better in this angle than Vim by far. You can find the documentation for every variable (describe-variable) and functions (describe-function) easily and jump to their source codes.
Comment · 3 years ago
Comment · 3 years ago
That is one of my questions too.

Use a low entropy things (I guess user's password would be not larger than 20 characters nowadays even using password managers) to encrypt a high entropy strings (PGP key).

Looks pretty weird to me.

Comment · 3 years ago
Hmm. I rely mores on server-side filter rules because I don't use native Mail client.
Comment · 3 years ago
Even if all the decryption resides in the app/web browser side, they can just silently change the code and inject some scripts to hijack the encryption routine.

Although they are open-source and can be scrutinized by anybody, it does not means that's what is run on the server side.

(Just say they have the capability; no accusation)

So at the end of the day, the question is whether you trust Proton or not. Encryption might not help in that case.

Comment · 3 years ago
For other functionality, I will say nothing because it takes time to implement features and Proton is not as big as Google.

But for PGP? You should treat it seriously, considering your target customers.

Comment · 3 years ago
It hurts the trust mostly.

If they cannot handle basic things like PGP correctly, how should I trust other part of their software. Especially they are a "Privacy-first" company.

"Privacy" becomes a marketing term nowadays.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton