A recent r/ChatGPT post, an experiment in iterative image generation, went viral for a simple reason: give a model an image and ask it to recreate it, repeat 70+ times, and the result slowly, hilariously, and alarmingly diverges.
Observations from the thread
According to top comments, the thread’s standout observations were twofold:
- the image steadily morphs, adding objects (a table and its reflection), changing chest shape into a flat surface, and introducing garish artifacts;
- the subject’s skin tone shifts toward darker hues, prompting jokes about a “Netflix raceswapping algorithm.”
One blunt comment summed it up: “The piss filter that AI images have made the AI think that she was black.” Another user noted the model inventing features that weren’t there at all: “I was wondering how well it preserved the reflection in the table, but then I went back to the beginning and there wasn’t even a table originally.”
Why does this happen?
- Iterative re-encoding (the image telephone effect)
When you feed an AI-generated image back into a model, you’re not giving it the original pixels; you’re giving it a noisy, re-rendered version. Small artifacts compound with each iteration. Over many rounds, that small noise becomes visible, structural distortion and invented elements follow, and identity drifts.
- Stochastic sampling and latent-space drift
Most image generators sample probabilistically from a latent distribution. Even with the same prompt, each pass produces a slightly different point in latent space. Repeating the process amplifies divergence.
- Dataset and tone biases
Models learn associations from training data. Color shifts are often the result of tone-map biases, color-space handling issues, or the model reverting to stereotyped representations when features become ambiguous after multiple passes. The result can be an emergent bias in skin tone or facial features.
- Hallucination of consistent but spurious details
The table-and-reflection example is exactly the kind of persistent hallucination that creeps in once the model latches onto a spurious pattern.
Why this matters
Repeated-generation experiments are a revealing stress test. They show how fragile identity and fine-grained details are under noisy pipelines, and they surface latent biases that otherwise live buried in training data. For practitioners, artists, and policymakers, the takeaway is clear: iterative or cascading AI processes can amplify errors and cultural biases in unexpected ways.
High-value comments worth calling out
- “The piss filter that AI images have made the AI think that she was black.” — blunt, but it captures how color and tone artifacts can be read as identity changes.
- “I was wondering how well it preserved the reflection in the table, but then I went back to the beginning and there wasn’t even a table originally.” — a neat encapsulation of how models invent persistent details.
Practical tips if you want to avoid or control drift
- Minimize chaining. If you must iterate, limit the number of re-generation rounds.
- Use deterministic settings where possible (fixed seed, lower sampling temperature) to reduce stochastic drift.
- Strengthen conditioning. Include explicit constraints in prompts: “Preserve original skin tone and facial proportions. Do not add objects not present in the source.”
- Use perceptual loss or identity-preservation tools when available (face encoders like ArcFace) to penalize divergence.
- For precise edits, prefer targeted image-editing over full image-to-image regeneration: mask the area and apply constrained transforms.
Remember that there is often another side to the story. This isn’t uniquely a ChatGPT failing; it is a class of behaviors inherent in many diffusion and generative pipelines, especially when pushed into long iterative chains. The viral thread is less an indictment of one system than a demonstration of a general phenomenon: noisy pipelines, probabilistic sampling, and biased training data combine to produce emergent and sometimes problematic outputs.
My takeaways
- Iterative image-generation experiments are an inexpensive, high-visibility way to surface biases and failure modes. Use them as tests, not as production workflows.
- If you care about fidelity, don’t rely on chained generations. Use stronger conditioning, deterministic sampling, and identity-preservation techniques.
- Public demos like this are useful: they spark discussion about bias, model evaluation, and the environmental cost (several commenters noted the carbon and compute expense).
If you enjoyed the thread, try a controlled version: run 5–10 iterations with gradually increasing constraints, log the exact seeds and prompts, and watch where and how the model diverges. It’s a small experiment with outsized lessons about robustness, safety, and the sociology of machine vision.
Leave a Reply