Wowsers! I just replaced my Nexcloud server. Rather than try migrating data I thought I’d just sync my local stuff to it.
The Nextcloud client went bananas and deleted most of my local stuff yet not all? Odd. Sweating bullets I was glad I made a local copy just before! So I’m rsyncing it back and am watching the NExcloud client sync it up again. That will include the Joplin stuff.
But I didn’t think to explicitly back up Joplin and was blown away when you failsafe notice popped up in the corner. Wow, thanks so much. But I have two requests:
Firstly the message could be clearer regarding data compromise. It says: Last error: Fail-safe: Sync was interrupted because 97% of the data (704 items) is about to be deleted. To override this behaviour disable the fail-safe in the sync settings.
I’m bamboozled. Why do the clients do this? Is this not crazy? The Nextcloud database knows nothing it certainly can’t report back that an item ever existed. I mean if it reported back that it once existed and was removed, then that should trigger a local remove. But if it reports back that it’s never heard of that item, surely that demands a push to cloud server? What am I not getting. Either way, the request is, to add to this message a really 100% clear indication of whether anything was lost or not. If the failsafe did not delete ANY local data that is WORTH saying explicitly and will save much angst. And if any was lost, please be explicit so we know what to shed tears over. But above all thanks from the bottom of our hearts for the failsafe.
The second request is for an explicit option to flag the server as new, and do a local push to remote. Force a local to remote push to start the ball rolling. It’s worth noting that floccus (which syncs to Nextcloud) has just such an option. And it rocks.