{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiehxijepv4nvmuu6kjt2iic76j7xu2jpklarzq3pvwhlr44qz7gtu",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mlgd5r675rz2"
  },
  "path": "/t/collection-of-gpt-image-generator-2-0-issues-bugs-and-work-around-tips-check-first-post/1379535?page=12#post_237",
  "publishedAt": "2026-05-09T12:02:05.000Z",
  "site": "https://community.openai.com",
  "textContent": "I think one difficulty with this test is that some of the “fantasy words” may not actually be neutral fantasy words.\n\nI googled a few of them, and at least some seem to already exist in some form. That means they may already carry associations from training data, search-like knowledge, brand names, names, or similar existing terms. So they are not completely neutral test inputs.\n\nEven if we use truly invented words, the model can still create associations based on:\n\n  * phonetic similarity to known words\n\n  * typical fantasy-sounding syllables\n\n  * the current chat context\n\n  * user memory or long-term project context\n\n  * previous image generation behavior\n\n  * the selected ChatGPT mode/model\n\n  * possible automatic prompt expansion\n\n\n\n\nSo I think this kind of test can still be interesting, but it is very hard to isolate what exactly is being tested.\n\nTo really reduce those effects, the test would probably need a very “cold” setup: no relevant memory, no long chat history, no project context, ideally a fresh API setup, and then the same prompts tested repeatedly across direct Image API, Responses API, and ChatGPT.\n\nOtherwise we may not be testing only the image model. We may also be testing the accumulated context and interpretation layer around it.",
  "title": "Collection of GPT-image-generator 2.0 issues, bugs, and work-around tips (check first post)"
}