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?
@Dave It actually works quite nicely with Tresorit. And the latency lag is acceptable.
I've been doing this via Rclone + Jotta Cloud with Rclone encryption, which still works better than Rclone + Proton Drive. But not as smooth as Tresorit. Rclone + Backblaze B2 + encryption is also better than the Proton Drive approach.
I've also used this approach in read-only mode with @borgmatic too, which is a great way to restore data from a backup. And that's almost as smooth as Tresorit (even though a very different use case).
I thought a bit more on these complaints since this post. And I realised these complaints can also be ignored by applying some basic mathematics and common sense.
Proton has more than 100 million users by now. So let's say 100 million in this example. How many public complaints would it need to be from these users to really "catch fire"? Meaning - how often do you read about complaints and from how many users? More than 100.000 users? Okay. Let's say there are 1 million dissatisfied users.
If half of that million users complained loudly on the Internet, I would say that would probably be quite noticeable. Media would most likely pick it up, and it would brew up to media storm right?
Have you noticed anything like that? Do you see that many users complaining?
And if yes, that would still only represent 0.5% of the whole user base of Proton. If you include the other half complaining "silently", it would represent 1% of the Proton users.
That still leaves 99% users which are at least to some degree satisfied with Proton.
Even if you pull it up to 20 million dissatisfied users, they would still be in the minority compared to users finding Proton's services being just fine. And 20 million dissatisfied users - that would definitely have caused some media traction, don't you think?
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.
Yupp, that's my understanding as well.
But Proton also insists on doing the packaging and distribution of it outside the ordinary distribution paths Linux distros uses (apt/yum/dnf repos or flatpak) ... So they waste time and energy on getting stuff working properly across a broader range of Linux distributions.
The end result will therefore most likely be a poorer user experience where some features don't work well on some distros. Depending on how their "package" will manage to integrate on the distro installing it.
Where did they say that? They don't even have possibilities for remote work?
There are few alternatives to Proton Drive. Filen.io is the closest one in features. But it's a small company, so it development takes time.
Another alternative is Tresorit. Feature wise it is far beyond Proton Drive and Filen, with more advanced sharing possibilities. But it's quite expensive, closed source and uses Azure under the hood on the server side.
Filen and Tresorit are the only ones with Linux apps. Proton Drive can be accessed via rclone, but that is quite slow tbh.
@unruhe @Tutanota @protonprivacy
Give both a shot. Both are the only ones (I know of) having zero storage access as the only option; meaning #e2ee is enforced. You may have mailbox.org as a third one (E2EE must be enabled manually there).
I ended up with Proton as I experienced it far more feature rich, flexible and mature. And the Bridge is a must for my use case. In addition, it builds on PGP which can be used to have E2EE communication with people outside of Proton. (yes, I've tried Mailvelope with Tuta; that does not work at all. And doing it manually with copy/paste and PGP in an ordinary text esitor is a waste of time and also turned out error prone one the receiving end; Tuta mails gets mangled on the way).
But if you're a very lightweight mail user, Tuta might fit your need. I generally think of Tuta more like a messenger service with SMTP transport support.
Also beware, importing mails to Tuta is still not possible (unless that has changed the last months). And exporting mails are also a mess. I have migrated one user from Tuta to Proton, and I had to manually fix mail headers to get them imported. The mail export was quite poor, tbh. It took me longer than importing a handful of users from a Zimbra server to Proton - using the same Proton Mail Import/Export tool.
Finally, I just want to mention that Tuta is a company with less than 20-30 employees, serving something like 10 million users. Proton is probably closer to 500 employees these days, serving more than 100 million users. So these organisations are quite different. Which also means they have quite different approaches for developing services further and capabilities to handle sudden challenges.
@jon@vivaldi.net I use a plethora of browsers.
I'm migrating fron Firefox to LibreWolf (sorry, I prefer non-chrome based browsers), but have a Ungoogled Chromium as a backup those times Firefox/LibreWolf doesn't cut it (I thought the world had learnt a lesson from the IE days; seems we need to educate a new generation web hipsters).
On Android I use the default browser (in @e_mydata@mastodon.social) for a few news/blog sites, Mull and Vivaldi for some other sites and DuckDuckGo when searching. Default browser is Mull with Privacy Mode enabled by default.
I honestly don't like that the Chrome based browsers seems to be dominating these days. We need a heterogeneous web render environment to ensure a single dominant player dictates how things will be for users.
And without such competition, I fear there will be a lesser drive to further improve browsers. Just like when Netscape seemed too complacent with their own browsers back in the days.