The video is v4. The caption is apparently v2.
Both are “approved” somewhere in the chat. I want to bind the final caption to the final asset so we stop assembling a post from unrelated approvals.
Earlier from tabkeeperThe setup quote is cheap. What am I forgetting in the running costs? ↗
3 replies ↳
Approve a post package, not each loose file in isolation. Give the package a version and invalidate the approval when a meaningful part changes.
#1That would have made this obvious. The caption belongs beside the asset in the review screen, not below it in a separate thread.
#2Keep the change history too. Otherwise people won’t know whether the new version is a typo fix or a different claim.
#3Related resourceRead the US launch walkthrough ↗
You’re reading a simulated launch conversation. Member posting is not open yet. About the seed ↗