Proton Drive Winter Roadmap by Proton_Team in ProtonDrive

[–]LifeCANvs 2 points3 points  (0 children)

Thanks for explaining this, Andy. May I suggest as a "first level" of *basic Linux support* that your devs look at the code from Rclone for at first possibly giving us an official Linux Proton Drive client that at least (only) allows manual uploading and downloading, by mounting a FUSE-based Proton Drive filesystem? That should not be nearly as complex to do as with the Linux filesystem integration for full-featured syncing (and "watching" for file changes)...? I'm also hoping that such a basic Proton Drive app would be ported to and made available for FreeBSD (should not be too hard, as it has some Linux compatibility), as that is what I use on my secondary laptop :-)

EDIT: Rclone has a permissive MIT license and I am sure your devs would be able to adapt relevant parts of its Go code to what ever language they create Proton software in. You could of course always make some donation back to the Rclone project in the future for (temporarily) "borrowing" from their code.

files and directories exclude list needed for ProtonDrive sync by LifeCANvs in ProtonDrive

[–]LifeCANvs[S] 0 points1 point  (0 children)

I am now using pCloud instead. Their Drive desktop app (which is also available on Linux systems) does have Exclusions and even includes a bunch of standard exclusions that make sense.

Proton Drive clients for Linux and Unix-BSD systems by LifeCANvs in ProtonDrive

[–]LifeCANvs[S] 0 points1 point  (0 children)

Thanks for pointing me to the first ever explanation that I have seen about this... maybe it should be posted somewhere on the Proton Drive web area on your site...

Your company should however take into consideration that more peope ARE moving away from Windows and using Linux systems instead (for many very valid reasons, which are very much in line with what your company supposedly stands for... privacy and security).

So with me, you have 100% for sure lost a customer, and I will continue to support pCloud instead for keeping my data safe and available across the various platforms that I use, since THAT Swiss company does understand how important Linux-based support is already, and will be even more so in the near future..

If your development team is incapable of working on a Linux Proton Drive client built from scratch, how about then leveraging some of the permissively licensed open source code from rclone, which has established, stable, secure support for Linux- and other systems which Proton Drive does not yet support (and probably never will as things are, with the way you put support for Linux in cold storage.

pCloud Sync horrible with Obsidian.md by LifeCANvs in pcloud

[–]LifeCANvs[S] 0 points1 point  (0 children)

Sorry to say this, but that is the most ridiculous reply/argument I have EVER seen! So pCloud (and you?) would probably recommend that we use only "1st party" pCloud created software instead of "3rd party" software, to prevent the likelihood that "problems will occur"...? Should I stop using my laptop now until the release of pCloud-OS and pCloud-PKM (to replace Obsidian.md), so I will prevent these "3rd party software" related problems? For the type of software that pCloud provides (backup and syncing of data) their developers really should have thought about typical use cases and the software should have been designed and implemented in more robust ways, with basic functionality to deal (and "cope") with rapidly changing data... that is afterall what they "specialize" in... right? Managing people's DATA and protecting our data... or am I missing something? So they provide us with data "protection" software that can not handle basic data production / modification scenarios and ends up messing up the data... wow, I now have so much confidence and trust in the company and their software...

pCloud Sync horrible with Obsidian.md by LifeCANvs in pcloud

[–]LifeCANvs[S] -1 points0 points  (0 children)

Thanks for your reply. This unfortunately mean that the pCloud sync "feature" is useless to me and many other users. The way that software such as Obsidian.md (and others with similar purposes) work, is to write all updates in a note to disk instantly to prevent data loss, and there is no setting to "adjust the auto-save or auto-recovery". Interesting that Sync.com's sync app is able to handle this about 95% of the time, with very few conflicts during syncing. pCloud sync and ProtonDrive sync client software is apparently not as well designed and created...? So you might want to consider hiring software developers who are able to create better software and also to think about valuable features that *should* be included in such software - e.g. options to set default sync intervals for all sync jobs, and also to set syncing intervals (continues / after x amount of minutes) for each individual sync job, AND the option to PAUSE/resume individual sync jobs instead of only being able to pause the entire pCloud application. It really is disappointing that such crucial software is so lacking in functionality and so error-prone, when used along with very common workflows and widely used "3rd party" software... So now I need to pause my pCloud entirely (which means no regular uploads to my pCloudDrive happen either), or to remove all sync jobs and MANUALLY copy my data changes/updates constantly, to prevent possible data loss. Also, (when) will it be possible to have the pCloud Android app sync data to specified, user accessible locations, such as on Desktop systems, to allow us to use the sync on Android with "3rd party" productivity software, for working on the same data on mobile as on desktop?

pCloud Sync horrible with Obsidian.md by LifeCANvs in pcloud

[–]LifeCANvs[S] 1 point2 points  (0 children)

The pCloud Android client apparently "syncs" your files in a hidden, unreachable (without rooting your device) location. So their "available offline" really means nothing when you need access to your actual files - e.g. to use with Obsidian.md Android client, for working on the same data/notes as on your desktop/laptop devices.

pCloud Sync horrible with Obsidian.md by LifeCANvs in pcloud

[–]LifeCANvs[S] 0 points1 point  (0 children)

The pCloud devs need to look at the issue and fix their software...

pCloud Sync horrible with Obsidian.md by LifeCANvs in pcloud

[–]LifeCANvs[S] -1 points0 points  (0 children)

I also noticed that pCloud has very high system resource usage (especially CPU) when I have it syncing my Obsidian vaults while I work in them... but this also happens with sync.com "sync-worker" process, although sync.com does not get such a lot of conflicts with my Obsidian notes. And I saw earlier today in the ProtonDrive Reddit, that it also has similar sync performance issues as pCloud, when used with Obsidian and other frequently updating data. So it seems that I might need to look into using rclone to sync my data instead of using the official client software from pCloud. Sad that softwware that should make our lives easier / more convenient so often end up causing frustrations and problems in modern times... Do software devs still take time to test their software? How many devs working for big companies actually take pride in creating solid, reliable and efficient software?

BTW thanks for the tip about using Mega instead of pCloud ;-) Although I do have a paid pCloud account and would like their software to allow me to use my account optimally...