<?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/32201bf5a1ca4a348ad16acfc257be8f&quot; frameborder=&quot;0&quot; width=&quot;1280&quot; height=&quot;960&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>960</height><width>1280</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>960</thumbnail_height><thumbnail_width>1280</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/32201bf5a1ca4a348ad16acfc257be8f-cbf8fa43a49a0fef.gif</thumbnail_url><duration>165.755</duration><title>Engineering Feed Database Schema Overview</title><description>This Loom explains the engineering feed database schema and the relationships between its tables. It starts with decisions around making the platform invite only, noting that the allowed users table was later dropped even though sign-in and a user table remain. It then details how block source seeds RSS feed URLs and relates one to many with blocks, while block to summary and simplify are one to one. It covers many to many relationships using intermediate tables for block prerequisites and block tags, plus one to many for feedback and LLM usage, and mentions a previously considered block junk table that was later dropped when search was removed since the core problem is discovery.</description></oembed>