Skip to content

Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.

fix(x-content): have the editor judge a reel's accessibility by the post, not by alt text

nirholas67bfec444e66
diff --git a/api/_lib/x-content/editor.js b/api/_lib/x-content/editor.js
index 714ebece4..6b9bae1e4 100644
--- a/api/_lib/x-content/editor.js
+++ b/api/_lib/x-content/editor.js
@@ -78,6 +78,7 @@ function reelRecord(item, row, proof) {
`Captions, in order: ${JSON.stringify(captions)}.`,
`The run read off the screen: ${JSON.stringify(proof?.facts || {})}. It waited for and saw: ${JSON.stringify(proof?.saw || [])}. The server answered: ${JSON.stringify(proof?.responses || [])}.`,
`Waits cut from the film, each labelled in the reel: ${JSON.stringify(proof?.cuts || [])}.`,
+ 'X accepts alt text on images and GIFs only, so a reel cannot carry one and its absence is not an issue. What a reader who cannot see the reel gets is the post: raise it as a clarity issue if the post alone does not say what the reel shows.',
].join('\n');
}