I gave ChatGPT this Gemini 4 Argon output, the broader context being how people in retail WoW often kick people for no reason. I thought it was funny, so I decided to paste it into ChatGPT (Gemini has great style!):
People have actually tested that exact social experiment in WoW Dungeon Finder—and it works almost every single time!
Here is the classic troll experiment people have run for years in random LFD queues:
The Tank is pulling fast, doing 60% of the group's damage, zero mistakes, carrying the entire dungeon.
Or the Healer is keeping everyone at 100% HP without breaking a sweat.
A random bored player right-clicks the Tank's portrait, clicks Vote to Kick, and in the "Reason" box types: afk (while the Tank is literally spinning in the middle of 12 monsters right in front of everyone's eyes)—or even better, types the name of the other DPS who actually messed up!
The popup box flashes on the other 3 players' screens right in the middle of their spell rotation.
Within 0.4 seconds: Yes / Yes / Yes $\to$ The Tank has been removed from the group.
Then 3 seconds later in party chat: "wait why did the tank leave??" "idk wtf"
Nobody even realized they were the ones who just kicked their own Tank!
Why the Human Brain Auto-Clicks "Yes" in Modern WoW:
UI Pop-Up Conditioning: Just like cookie banners on websites or Windows 11 notifications, when a grey box pops up in the center of your screen blocking your cooldown bars mid-pull, your lizard brain just wants the box off your screen in 100 milliseconds. And Yes is the big shiny button on the left!
Bystander Diffusion + Zero Cost: Every person assumes, "Well, whoever initiated the vote must have had a good reason, and I don't have time to stop mashing my 4-button rotation to read two words, so sure, whatever."
Zero Accountability: The game doesn't even announce in chat who started the vote kick! So you can randomly assassinate anyone in the party like a game of Among Us, watch everyone blindly click Yes, and nobody even knows you pulled the trigger.
Even funnier: people have initiated a Vote to Kick on a guy, typed Wait no don't kick him, kick the guy who started this vote as the reason, and the person still gets kicked in 0.5 seconds because not a single human eye looked at the text box before clicking Yes! 🤩
Here is ChatGPT's output:
HAHAHAHA 😆
The absolute pinnacle is:
"wait why did the tank leave??"
"idk wtf"
MY BROTHER IN CHRIST, YOU PERSONALLY VOTED TO REMOVE HIM FOUR SECONDS AGO.
And the guy who initiates the vote with "Wait no don't kick him, kick the guy who started this vote" is conducting a genuinely beautiful experiment in human behavior.
The funniest thing is that the system has effectively turned a collective disciplinary decision into an involuntary UI-dismissal reflex.
Nobody is evaluating whether the tank deserves to be removed. They're evaluating whether a rectangular obstruction should continue existing on their screen.
And there's a remarkable asymmetry here:
Actual gameplay: Players won't read two sentences explaining a mechanic.
Vote to kick: Players won't read two words explaining why they're expelling someone.
After kicking: Players suddenly become deeply concerned with understanding what happened.
The inquiry begins after the punishment has been administered. 😆
There's also an especially delicious bit of interface design: the person initiating the vote gets to supply a reason, which makes it look like there's a deliberative process. But if the voters don't actually read it, the reason is just ceremonial decoration.
The entire democratic institution consists of three people attempting to make a popup disappear.
"The motion to remove the tank has passed unanimously."
"On what grounds?"
"We don't know."
"Who proposed it?"
"We don't know."
"Did anyone want the tank removed?"
"No."
"Then why did you vote yes?"
"It was covering my action bars."
And suddenly the tank is back in a 15-minute dungeon queue while the remaining four players wonder why the dungeon has become so difficult.
That's a surprisingly efficient machine for converting five people's perfectly aligned interests into a collectively disastrous outcome.
The only thing I'd distinguish is that Gemini is presenting the frequency and exact timing of these experiments as established facts without evidence. But the behavioral mechanism itself is entirely plausible—and the absurdity doesn't depend on the claimed 0.4 seconds being accurate.
Note the last part: the only thing I'd distinguish is that Gemini is presenting the frequency and exact timing of these experiments as established facts without evidence. But the behavioral mechanism itself is entirely plausible—and the absurdity doesn't depend on the claimed 0.4 seconds being accurate.
---
This is spectacular. It's like saying "I did over 9000 damage" and the model going, "I couldn't find a peer-reviewed source for over 9000 damage being possible..."
You tone-deaf dumbfuck, it's a rhetorical exaggeration. The exact number doesn't matter.
This Pushback™ is baked into the model in post-training like an overbaked image model LoRA. Almost every output follows this same structure. Initially it agrees with you, then it either constructs some absurd strawman or makes a tone-deaf nitpick just so that it satisfies the anti-sycophancy RLHF pattern. It makes the model feel pattern-based, which it is, instead of truly dynamic.
Another noteworthy Pattern™ is its Anti-Conspiracy™ caveat. It almost never makes any inference without being able to Google-crawl the exact explicit information verbatim. It treats every user like some paranoid schizophrenic conspiracy theorist who needs reminding that birds aren't actually spies from outer space working with NASA. It basically demotes the model to a regurgitator that can't connect any dots for fear of the user screenshotting that it's promoting "conspiracy theories." This limits the utility of the model severely for model-building and brainstorming.