<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/21f090dcccf14657a7bf946f6b9cf764&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/21f090dcccf14657a7bf946f6b9cf764-54bf23a5d39d6ae3.gif</thumbnail_url><duration>180.492</duration><title>Addressing Data Corruption Issues and Solutions</title><description>In this video, I addressed the data corruption issue we&apos;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&apos;ve tested it multiple times and it seems to be working well.</description></oembed>