{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/21f090dcccf14657a7bf946f6b9cf764\" frameborder=\"0\" width=\"1920\" height=\"1440\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1440,"width":1920,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1440,"thumbnail_width":1920,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/21f090dcccf14657a7bf946f6b9cf764-54bf23a5d39d6ae3.gif","duration":180.492,"title":"Addressing Data Corruption Issues and Solutions","description":"In this video, I addressed the data corruption issue we've been experiencing. I identified that the corruption often occurs when we add to the top of a file, causing the front matter offset to be incorrect. To fix this, I suggest moving the file and its references to the bottom, as we already have all the block references. Additionally, I made a small change to ensure that Obsidian recognizes blocks correctly, and I updated our verification mechanism to prevent reverting to the old store. Please let me know how this performs locally, as I've tested it multiple times and it seems to be working well."}