I just migrated my space from one host to another. I preserved all the file attributes (thanks, rsync, you rule) so that the file creation dates would be correct on my new host. I've verified that they are in an ssh session.
Once my new space re-indexed, all my creation times matched the date the note was indexed, not the date it was created according to the file system. I thought it matched the file creation date.
I was hoping to rely on the file metadata to order my notes in some cases. For example, I'd like it if my journal entries didn't depend on a naming convention to be ordered but could use the created date. I have this whole thing about structured vs. unstructured data. ![]()
It looks like lastModified works this way, but if I can't use it as a stable "created on" ordering. If I ever edit something in a note, it'll get messed up.
I found this bug where someone had a similar experience: Note creation timestamp not recorded correctly in index · Issue #1714 · silverbulletmd/silverbullet · GitHub
I did some random checks (restarted the containers, pulled latest, etc) and it looks like the https://my.private.sb/.fs entries all have created attributes that are very close in time to each other, so this looks like a server thing.
Any chance I can vote up this feature request? Anyone else doing something similar?