Have you tried Proton Docs? While not the exact same thing as Standard Notes, the editing and history seems to be quite similar. All "notes" files are stored in Proton Drive too.
Or are there other features in Standard Notes not to be found in the Proton suite?
I can understand the confusion. But it kinda makes sense.... if my hypothesis is correct.
Proton Drive has the concepts of "My Files" and "Computers". Files stored under "Computer" (where you can have synced files for up to 10 computers, according to docs) tracks the files for each computer individually.
So when you uninstall Drive and delete the files, they are only stored in the cloud. But after reinstalling it again, it sees the files locally for that computer is gone ... so it gets removed in the cloud.
Had these files been moved to "My Files" in before the reinstall, this should not have happened.
At least, that's my theory.
They could even have a Fedora Copr repo, where they push out the updated .spec file and get a proper package build for all Fedora, RHEL/CentOS and more distros. With proper RPM packaging and repository. Push a new build and all users gets an updated package at their next update cycle.
That's a reasonable path to get started with preparing packages to become part of the native yum/dnf repos at least. And that across a lot of distributions and releases in a single go.
@LinkOpensChest_wav @helenslunch
I've done the self-hosting of e-mail for over a decade. But it got so annoying and troublesome in the end it was a delight to migrate to Proton (because of all the spammers making this whole e-mail infrastructure a nightmare).
Incoming e-mail is still doable for self-hosting. But outgoing is getting incredibly hard when you're a tiny actor; you get blocked by all these larger mail providers (gmail, hotmail/outlook.com, yahoo) and your just lucky if you're able to get in touch with anyone willing to look into the issues. Most times you get a mail template back claiming a bad IP address/range reputation (despite being able to document it several years back). The worst one even claimed I did aggressive marketing spam (which would be absurd for the handful users I served, used it for private emailing). And then they close the support ticket and ignore you.
Proton is definitely big enough to fight back such abusive behaviours by these large actors.
@8rhn6t6s There are some caching which need to be enabled with the protondrive rclone mounting. But it is still slow.
Remember that non-E2EE storages (such as Google Drive, AWS/S3, etc) can do the upload a lot faster as a starting point, as there is no client-side encryption of the data being uploaded (and the reverse; decrypting downloaded data). This decryption/encryption happens in the protondrive "module" in rclone. On top of that comes that files are split up into "chunks" which are transferred via separate HTTP calls. And I have no idea (aka "have not read the code) how the unlock key of the PGP key is handled in rclone. All of these things combined together impacts the performance.
That said, I've had a quick test on a Windows computer with Proton Drive installed. It wasn't blazingly fast there as well, but still felt faster than rclone.
My guess is that it's partly that the rclone implementation has room for improvements on how the Proton Drive server-side APIs are called and some of it is related to crypto implementation performance.
For example, I dunno if the Proton Drive APIs support HTTP/2 protocol or QUIC ... And I dunno if the rclone supports them as well. Just in this aspect there are lots of room to cut down on the "connection handshake" as HTTP/2 and QUIC supports more efficient handshakes and can also have multiple streams sending data in parallel - using a single handshake. If the native Proton Drive app on Windows implements this, that may explain some of the performance differences.
For my own stuff, I do prefer Bitwarden over Proton Pass. Simply because having a lot of stuff in Proton and if then ending up being locked out feels like a too high risk.
I even have some stuff in https://www.passwordstore.org/ where it's synchronised to some (encrypted) locations and internal storage servers ... especially stuff which can help me if I get locked out of Bitwarden.
Don't put all your eggs into the same basket. Avoid the SPOF.
That said, for Proton accounts where I'm the admin - I would recommend Proton Pass these days, as it provides ease of convenience. Where less technical users has only one "platform" to relate to. If these users gets locked out; I have a chance to help them recovering again.
@0x0 @codeinabox it wouldn't be EEE in this case. Because a Linux distribution is built up around thousands of packages from hundreds of various open source projects.
For EEE to work, the entire base OS stack would need to be extended with features not becoming useful outside Microsoft's use. Such changes would first of all have a really hard time being accepted in upstream projects. And if they did, these projects would be forked if the last E phase in EEE is triggered. And then Microsoft would be alone with their Frankenstein distribution monster while the majority of the Linux users moves on to something better.
With Linux, there is no single instance of control or power. If a project takes a path people don't like, it get forked. EEE requires Microsoft to cease full control of all the related pieces and components and kill the open source aspects of it.
That's the advantage of open source licences. Once the source is out in the public, you can't retract the source code afterwards, then it just forks.