<?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/ae2f845d4b7c48e0a74adfdda12bb5bc&quot; frameborder=&quot;0&quot; width=&quot;1662&quot; height=&quot;1246&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1246</height><width>1662</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1246</thumbnail_height><thumbnail_width>1662</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/ae2f845d4b7c48e0a74adfdda12bb5bc-4f4dd88a108d6f0c.gif</thumbnail_url><duration>208.318</duration><title>Fixing Obsidian Import URLs and Collisions</title><description>This Loom explains updates to Obsidian import logic to handle new schema-related behavior and fix detected bugs. The author describes code churn to address issues such as Firebase URLs not being detected correctly, along with other import problems. They then test that Roam pages download all files from Superbase successfully, that schema.svg has proper local URLs, and that identical schemas resolve to the same asset file. Finally, they test the collision case by importing an issue with a different schema file and adding hashing to distinguish it.</description></oembed>