{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/91078efd00b14f959ebf0ba07950a4fe\" frameborder=\"0\" width=\"1662\" height=\"1246\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1246,"width":1662,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1246,"thumbnail_width":1662,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/91078efd00b14f959ebf0ba07950a4fe-4b2e528eabc60588.gif","duration":483.577,"title":"Sending Roam Data to Superbase, End to End","description":"This Loom walks through a large multi-step PR for sending ROAM data and assets to Superbase. It details utilities and tests for detecting ROAM asset reference patterns, fetching asset metadata and data from Firebase, and copying assets to shared storage with size checks and failure handling. The publish logic then reuses existing references when possible, removes unreferenced assets, publishes asset results per app cross app, and sends the copied assets to Superbase while tolerating individual failures. The final export reports counts of failures, assets too large, and unresolved push outcomes."}