One question for AT Proto as a blog backend is whether users will want a single record in their PDS that works across Bluesky clients and custom platforms. In that case, a custom “full-length post” embed inside Bluesky’s own lexicon seems to make the most sense. I don’t want to reinvent the wheel.