It means we remain backward compatible for users who are currently synchronising with pCloud.Įdit: In fact, we can have a migration step - if during the upgrade we detect the user is using one of the unsupported implementations, we automatically set the Advanced option to 'true'. If On, we allow sync but at the user's own risks. Because of this, we should add an option in Advanced settings - 'Allow sync with pCloud' (with a description). That way the user is immediately alerted and can switch to a different sync target without committing to pcloud.Įdit: We don't know the full story - it's possible that for certain use cases, pCloud work fine, maybe for small notes or not many notes, so some users might already be using it.

Pcloud has a faulty WebDAV implementation and as such Joplin no longer supports it. So we should deal with it on our end: if pcloud is detected, we immediately stop sync and throw an error explaining the situation. It uses our resources and it makes it look like Joplin is unreliable, even though it's not possible on our end to fix the issueĪlthough their implementation is broken, it stills works well enough that a user might rely on it, not realising that they are losing notes or that some data get corrupted. Users incorrectly think that it's a problem with Joplin and come for us for support. The only reply we got from them was essentially blaming Joplin, even though the apps sync fine with dozens of other standard WebDAV services.

Pcloud is a popular cloud service, however their WebDAV implementation is broken and have been so for a long time.

Pcloud webdav url