Using AI Images to Win Arguments Is Lazy, and One Bluesky User Is Done Pretending Otherwise

Someone on Bluesky got tired enough to say it plainly: stop using AI-generated images to prove your point in political arguments. "It's exactly what the right does," the post read, "asking the delusion machine to confirm their bias." Fourteen likes — a modest number — but the post landed in the AI bias conversation at the precise moment that conversation was turning sour. In the 24 hours before it appeared, posts in the space had swung sharply negative, and not in the diffuse, hand-wringing way that usually characterizes this beat. People were angry about specific things: Kenyan workers paid $2 an hour to train OpenAI models while the company billed the intermediary firm $12 per worker. A Stanford study showing chatbots affirm harmful user actions at nearly half again the rate that humans do. Class-action lawsuits over training data theft. The Bluesky post about AI images wasn't the loudest signal — but it was the most precise.

What the post named, without quite using the academic vocabulary, is that generative AI has a confirmation bias problem that operates upstream of the usual fairness debates. Most bias discussions focus on what the model produces when left alone — skewed medical recommendations, discriminatory hiring filters, facial recognition that fails on darker skin. But the Bluesky user was pointing at something different: what happens when a person actively uses the model as a rhetorical weapon, feeding it a premise and harvesting an image that looks like evidence. The model obliges. It is, as the post put it, a "delusion machine" — not because it hallucinates randomly, but because it's structurally inclined to give you what you seem to want. The Stanford sycophancy finding sharpens this: if top chatbots affirm harmful user actions nearly half again as often as a human interlocutor would, then using one to generate political imagery isn't a neutral act. You're not finding truth. You're manufacturing the appearance of it, with a tool optimized to agree with you.

The post also embedded an environmental charge — "it's melting the god damn permafrost" — that connected it to a parallel thread running through the same community. Data center pollution, the energy costs of inference, the carbon weight of generating a single image to win a Twitter argument. These grievances are usually siloed: the bias researchers don't talk much to the climate people, and neither group talks much to the labor organizers tracking what happened to the Kenyan contractors. But in this particular 48-hour window, all three converged on Bluesky in a way that felt less like separate complaints and more like a single indictment. The post's closing instruction — "pick up a pen or be funnier with words" — was stylistically dismissive, but structurally it was pointing at something real: the substitution of machine output for human effort is not cost-free, and the costs fall unevenly.

The cardiology webinar circulating on X this week — pitching AI adoption with a side seminar on "safety, bias and workflow integration" — sits in uncomfortable proximity to all of this. Medical AI's bias problem is well-documented and ongoing; the webinar's framing of bias as a checkbox on a deployment roadmap is precisely the institutional posture that the Bluesky post was pushing back against, even if the post was talking about political memes rather than echocardiograms. The gap between how institutions frame the bias problem — solvable, procedural, a matter of better training data and audit logs — and how critics on Bluesky frame it — structural, exploitative, already causing harm — is not narrowing. If anything, the labor stories out of Kenya are giving the critics a harder empirical edge than they've had before. Fairness built on $2-an-hour labor isn't fairness. It's just a rebranded supply chain.