Thank you, and I appreciate that. The behavior is very easily reproduced, so I do not understand the delay in diagnosis. As I said before, it seems to be very simply bad/incomplete distributed data management practices in the core logic. I’ve worked with distributed systems at work for maybe 20+ years, and there are well established standards for how to manage data synchronization to avoid the most common issues, such as the replication of deleted or moved files from one node to another which is more current.
Is there continuing good faith effort to address that algorithm or adopt a better standard (was your team able to review the standards for Log-Structured Merge-Trees (LSM-Trees) and Tombstones like Cassandra uses, per my recommendation in January), or has this been tabled?
Honestly when we develop software, the biggest boon to resolving issues is persistent logging, which we still do not have (what good is a log that doesn’t exist?).
I really want to love Obsidian and I mostly do, but over the last 3 years I have gone from an advocate of the tool, suggesting everyone and any one use it, to a vocal detractor of the paid component of the tool. Before I quit my subscription and contribution to your project and move to advocating against it, I want to be sure I’m in the right to do so. However, with problems here on what are basic issues we solved in software development back in 2010 and earlier and logging standards which we built the entire software industry on dating back to the 90s, I am very much starting to struggle.
Obsidian changed my life. It’s made everything far easier to handle and I’ve used it to build entire new tools that are helping people throughout two industries, and I WANT to be a strong advocate and pay you guys, but this is starting to feel like bad faith development.. and if that is the case, I can’t myself in good faith do so.. Our data is vital to our lives and its integrity far outweighs any fancy new feature, no matter how cool.