remotely-save: [Bug]: Daily notes and sync algorithm

What happened?

First of all, this is not a real bug, but IMHO a consequence of the current sync algorithm.

Context

I’m using your plugin to sync between my Phone and my Laptop. Both my editors are configured to Open Daily Note on Startup

obsidian_daily_notes_on_startup_settings

Configuration

I’m using WebDAV to synchronize my files.

Remotely save sync settings on my Laptop

obsidian_remotely_save_settings

How the “problem” was identified ?

This very morning, at 9:00 AM I’ve added a note on my Phone in my daily journal named journals/2024-02-18.md. I’ve manually triggered a sync and everything went ok.

A little later, I’ve turned on my computer. The file journals/2024-02-18.md did not exist at this moment. I’ve launched Obsibian as usual, and landed on my Daily journal note for the current day journals/2024-02-18.md .

On startup, this file does not exist and Obsidian creates an empty note file. Then, synchronization is triggered and the file journals/2024-02-18.md present on my Laptop is compared to the remote version of the same file (uploaded by my Phone). The local empty version of the file was created with a more recent timestamp and thus is keeped. Consequence: the note on my Phone is lost.

We can see that in the debug logs of my Computer:

obsidian_remotely_save_journal

Decision: uploadLocalToRemote

I know this is expected behavior. You have clearly described how your sync algorithm is working ✔️

Do you see any workaround for such behavior ? Has anyone already reported something similar ?

What OS are you using?

Linux

What remote cloud services are you using? (Please choose the specified one if it’s in the list)

webdav

Version of the plugin

0.3.40

Version of Obsidian

1.5.3

Using password or not

  • Yes.

Ensure no sensitive information

  • I ensure that no sensitive information is submitted in the issue.

About this issue

  • Original URL
  • State: closed
  • Created 4 months ago
  • Comments: 16 (8 by maintainers)

Most upvoted comments

I am considering adding “keep large file if conflict” may be it should partially solve the problem