<?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/2c08071a85d849f0b13e828541a0a429&quot; frameborder=&quot;0&quot; width=&quot;1670&quot; height=&quot;1252&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1252</height><width>1670</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1252</thumbnail_height><thumbnail_width>1670</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/2c08071a85d849f0b13e828541a0a429-77ba37f1436aa1cd.gif</thumbnail_url><duration>104.32</duration><title>Clarifying InsertBackLink Default Behavior</title><description>This Loom discusses adjusting InsertBackLink behavior so it matches user intent instead of always applying backlink insertion. The author explains that when a user opens the modal from an existing node, the default should be InsertBackLink to reference that node, while calling the command otherwise should result in no backlink behavior. They also describe that when there is selected text and the modal is invoked, it is assumed the user wants to create a backlink. Finally, they note that attempting to create a node using selectedText and createNode without going through the intended flow leads to nothing being replaced, though the created node still appears.</description></oembed>