dazo

@abobla

I kinda struggle to believe it's that difficult. I mean, Tresorit has a pretty good and functional Linux client. What have they done which makes it sustainable for them?

Filen.io also has a pure sync-client, which is distributed as an AppImage. This also works, but the FUSE integration Tresorit provides is quite awesome and performing quite decently.

I would actually recommend Proton to start the development on an older Linux distro. Like RHEL/Alma/Rocky 9 or Debian 11 (which is EOL, though) and make it run there. Moving from that distro to newer distros will then go smother and you'll get other distros supported quicker.

The mistake too many Linux efforts does is to take the "latest and greatest" distro version - often coupled with what a single Linux developer considers the "most used distro" and then hits lots of challenging when needing to support older distros. That's going to be painful.

@protonprivacy Please take note and forward to Andy and other managers.

@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).

@Dave @apples_and_pears

I've used Rclone with Proton Drive to mount a directory .... it is dreadfully slow. Maybe directory/file sync (where copies are both places) are better.

I cannot recommend Rclone for Proton Drive in "mount mode" currently.

@protonprivacy This is why I'm still using Tresorit on Linux .... One of two reasons (the other one is access to shared folders with read/write access).

@Dark_Arc @bl4kers

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.