We recognize that we still need to address other optimizations and fixes. This improvement is yet another step in our commitment to deliver reliable, fast, and secure apps for you.
Let us know what you think, and please keep your feedback coming!
I recently read that the Linux client is something that might not happen for a long time, if at all. The user base is too small and it doesn't make sense economically etc.
I have been hoping that a company that values privacy would see the benefit of people switching to Linux, and that having first-class support for Linux clients would be valuable in itself, as a message about Protons values.
If there's no money, then that's unfortunate. But the free and open source community has been known to put in a lot of work when there's a need. Would it be possible to make it easier for people to work on a community client? The main thing needed from Proton would be documenting the API I guess.
Is Proton interested in working together with the free and open source community?
Yeah some Up/Download + simple management API would be really nice. Since Proton is loved a lot among programmers, I'm very sure there'll be a lot of people in the community to create some implementation their own (including me)
And Andy(CEO) replied
This is actually good/important input. We went this direction with Proton VPN on Linux and the first version was a community built version which as OK. Eventually, we had to take the effort in-house to ensure it was sufficiently well maintained and keeping up with the latest features, but it was still a goo way to get started. We will indeed consider this for Proton Drive also, although it is a more complicated product (includes complex parts like sync engine and version conflict resolution logic, etc). -Andy
Oh that sounds good! I would also prefer rclone. I'm using the protonvpn through the native gnome network manager + ovpn profile rather than having to add some third party repo or the community flatpak.
I wonder if that "he should have access" means that the API specs can be public information or more like "we trust henry but it's still secret."
I guess we'll have to wait and see what happens next.