Sora 2 and the feed nobody asked for
A better video model wrapped in a social app, with a cameo feature that makes consent the whole product question.
OpenAI released Sora 2 alongside a standalone social app: a vertical video feed of AI-generated clips, with a "cameo" feature that lets you insert a verified likeness of yourself or a consenting friend into generated videos.
the model#
Genuinely better than the first version, in ways that matter:
- Synchronized audio. Dialogue, effects, ambience generated with the video.
- Physical plausibility. Objects have more consistent mass and momentum. Things that fall, fall correctly. Water behaves like water.
- Failure realism. A demonstrated example: a basketball shot that misses bounces off the rim, rather than teleporting into the hoop because the model learned that shots go in. Modeling failure states is a meaningful step toward actual physics rather than outcome mimicry.
- Multi-shot consistency. The same character and setting across cuts.
the app#
A TikTok-shaped feed where every video is generated. OpenAI's stated framing is creation over consumption, with feed controls and usage prompts.
I am skeptical, and the skepticism is structural rather than about intent. An infinite feed of content optimized for engagement has one known equilibrium, and it does not depend on whether the content is human-made. If anything, generated content removes the last friction — there is no supply constraint at all.
The genuinely novel bit is cameos: a verified likeness capture, with control over who can use it, revocable, with notification when it appears in someone's video.
That consent architecture is thoughtful. It is also the thing that will be stress-tested immediately, because likeness in generated video is the single most socially dangerous capability in this space and "we built a consent flow" is a much better answer than most products have.
Revocation is the hard part. You can revoke permission going forward. You cannot revoke a video someone downloaded.
the rights problem#
Reporting around the launch indicated a rightsholder posture that put the burden on IP owners to opt out rather than requiring opt-in, with an announced shift toward more granular controls after pushback.
Opt-out for likeness and IP is a defensible engineering default and an indefensible ethical one. It puts the cost of protection on the person being depicted, who may not know the product exists.
I expect this to be litigated and legislated, in that order, and I expect opt-in to win for likeness specifically because that is where the political consensus already is.
for developers#
The API is available and the practical questions are the same as for image generation, more sharply:
- Provenance metadata on everything. C2PA, watermarking, whatever your pipeline supports. This is going to be a requirement, not a nicety.
- Consent flows for likeness, designed in from the start. Retrofitting consent after you have a user base is a nightmare.
- Understand your jurisdiction's rules on synthetic media. They are being written right now and they differ substantially between the EU, several US states, and everywhere else.
the broader read#
We are about eighteen months from generated video being indistinguishable from recorded video for a casual viewer, and the social infrastructure for that — norms about disclosure, verification for journalism, legal standards for evidence — does not exist.
The technology is arriving considerably faster than the institutions. That is not a new observation, and it has rarely been this compressed.
— Dom, September 30, 2025